Details

    • Type: Feature Request Feature Request
    • Status: Closed Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 6.0.0.M1
    • Component/s: JCA service
    • Security Level: Public (Everyone can see)
    • Labels:
      None
    • Similar Issues:
      Show 9 results 

      Description

      This will allow the VM to exit after server shutdown. Alternatively, you may kill the Thread upon service undeploy. (Suggest the daemon route)

      "JCA PoolFiller" prio=1 tid=0x00007f72312ae3a0 nid=0x373 in Object.wait() [0x00007f7234efc000..0x00007f7234efcbf0]
      at java.lang.Object.wait(Native Method)

      • waiting on <0x00007f7261b17938> (a java.util.LinkedList)
        at java.lang.Object.wait(Object.java:474)
        at org.jboss.resource.connectionmanager.PoolFiller.run(PoolFiller.java:87)
      • locked <0x00007f7261b17938> (a java.util.LinkedList)
        at java.lang.Thread.run(Thread.java:595)

        Issue Links

          Activity

          Hide
          Andrew Rubinger
          added a comment -

          Now I suggest the "undeploy" route. The server should leave the VM in the same state is was before it started.

          Show
          Andrew Rubinger
          added a comment - Now I suggest the "undeploy" route. The server should leave the VM in the same state is was before it started.

            People

            • Assignee:
              Jesper Pedersen
              Reporter:
              Andrew Rubinger
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: