Bug 1475183 - Thread leak and OutOfMemoryError on JBOSS EAP 6.4.11 using jboss-client.jar, calling an EJB on EAP
Thread leak and OutOfMemoryError on JBOSS EAP 6.4.11 using jboss-client.jar, ...
Status: NEW
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB (Show other bugs)
6.4.11
Unspecified Unspecified
unspecified Severity urgent
: ---
: ---
Assigned To: jboss-set
Jiří Bílek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-26 03:46 EDT by velmayil subramanian
Modified: 2017-07-26 03:47 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Therad dump when we got the issue.. started application try communicate 20 times to another EJB server which is running on the same server with different profile. (97.69 KB, text/plain)
2017-07-26 03:46 EDT, velmayil subramanian
no flags Details

  None (edit)
Description velmayil subramanian 2017-07-26 03:46:14 EDT
Created attachment 1304622 [details]
Therad dump when we got the issue.. started application try communicate 20 times to another EJB server which is running on the same server with different profile.

Description of problem:

There is a web project on jboss eap6.4.11 which calling EJB to EJB using  jboss-client.jar cause the thread leaks and OutOfMemoryError.

we are using ejb2 for our application.

Version-Release number of selected component (if applicable):
JBOSS EAP 6.4.11

How reproducible:

more number of Simple EJB to EJB call using jboss client jar.

Steps to Reproduce:
1.Start the application using domain mode. 
2. try co communicate one profile to another profile using jboss client jar.


Actual results:

communication success and check the below log thread leaks. 

Expected results:

communication success and no resource and thread leaks.

Additional info:

2017-07-26 12:54:49
Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.71-b01 mixed mode):

"ejb-client-context-tasks-17-thread-1" daemon prio=6 tid=0x0000000018d50000 nid=0x211c waiting on condition [0x000000000c84e000]
   java.lang.Thread.State: TIMED_WAITING (parking)
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <0x00000000fab08768> (a java.util.concurrent.SynchronousQueue$TransferStack)
        at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
        at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
        at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:359)
        at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:942)
        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)

   Locked ownable synchronizers:
        - None

"ejb-client-context-tasks-16-thread-1" daemon prio=6 tid=0x0000000018d66000 nid=0x24bc waiting on condition [0x000000000c74e000]
   java.lang.Thread.State: TIMED_WAITING (parking)
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <0x00000000fab08be8> (a java.util.concurrent.SynchronousQueue$TransferStack)
        at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
        at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
        at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:359)
        at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:942)
        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)

   Locked ownable synchronizers:
        - None

"ejb-client-context-tasks-15-thread-1" daemon prio=6 tid=0x0000000018d68000 nid=0x7bc waiting on condition [0x000000000c64f000]
   java.lang.Thread.State: TIMED_WAITING (parking)
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <0x00000000fab09068> (a java.util.concurrent.SynchronousQueue$TransferStack)
        at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
        at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
        at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:359)
        at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:942)
        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)

   Locked ownable synchronizers:
        - None

"ejb-client-context-tasks-14-thread-1" daemon prio=6 tid=0x0000000018d62000 nid=0x267c waiting on condition [0x000000000c34f000]
   java.lang.Thread.State: TIMED_WAITING (parking)
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <0x00000000fab094e8> (a java.util.concurrent.SynchronousQueue$TransferStack)
        at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
        at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
        at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:359)
        at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:942)
        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)

   Locked ownable synchronizers:
        - None

Note You need to log in before you can comment on or make changes to this bug.