Unable to undeploy an application when it is running long time EJB calls.

To update an application that is running, replace command from the management console is used. Therefore, first, the application needs to undeploy.

After org.jboss.as.web.deployment.WebDeploymentService.doStop, ServerService Threads keep in WAITING state waiting all active ejb invocation to finish:

"ServerService Thread Pool – 116" prio=10 tid=0x00002b5cdce97000 nid=0x6d68 in Object.wait() [0x00002b5d10d0b000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)

• waiting on <0x00000005c5447f68> (a java.lang.Object)
  at java.lang.Object.wait(Object.java:503)
  at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory.shutdown(ShutDownInterceptorFactory.java:111)
• locked <0x00000005c5447f68> (a java.lang.Object)
  at org.jboss.as.ejb3.component.stateless.StatelessSessionComponent.stop(StatelessSessionComponent.java:135)
  at org.jboss.as.ee.component.ComponentStartService$2.run(ComponentStartService.java:72)
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
  at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
  at java.util.concurrent.FutureTask.run(FutureTask.java:166)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
  at java.lang.Thread.run(Thread.java:724)
  at org.jboss.threads.JBossThread.run(JBossThread.java:122)

Locked ownable synchronizers:

• <0x00000005ba6adf98> (a java.util.concurrent.ThreadPoolExecutor$Worker)

However, the application has some managed beans that do long time calls to a EJB method using remote invocation. DC and HC "hang" before the EJB call finish.

JBoss could have a time out to the undeploy.

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

JBoss EAP 6.1.1

Actual results:

The application does not undeploy intermittently.
DC and HC "hang" (they disconnect to each other) and it is necessary to restart all Hosts.

Expected results:

After some time waiting, the undeploy is forced to finish.