0 Replies Latest reply on Mar 15, 2016 10:54 AM by Tiberiu Tofan

    Wildfly 8.2.0 @Asynchronous EJB and ManagedExecutorService problems

    Tiberiu Tofan Newbie

      Using an @Asynchronous EJB deployed on a Wildfly 8.2.0 container results in the EJB not being invoked after a period of inactivity. Querying the thread-pool using cli reports 0 threads as being active.

      All the threads from the pool are in the waiting state:

      "EJB async-pool - 3" prio=6 tid=0x000000001656c000 nid=0x3bf8 waiting on condition [0x000000006b4fe000]

         java.lang.Thread.State: WAITING (parking)

        at sun.misc.Unsafe.park(Native Method)

        - parking to wait for  <0x00000000c09a4620> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)


      I also tried using a ManagedExecutorService wrapped in an ExecutorCompletionService which resulted into a dead-lock after the underling thread-pool was filled. Using a lower number of threads than the size of the pool works smoothly and thread pool is reused correctly, but as soon as the thread pool is completely used the service becomes unusable.

      Has anyone experienced similar problems?