[ https://issues.jboss.org/browse/WFLY-9900?page=com.atlassian.jira.plugin.... ] Richard Janík commented on WFLY-9900: ------------------------------------- Unfortunately no, the clients are simply stuck in awaitResponse: {noformat} "Runner - 565" #638 daemon prio=5 os_prio=0 tid=0x00007feb9841d000 nid=0x7f47 in Object.wait() [0x00007feaeb593000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:866) - locked <0x00000006826573b0> (a java.lang.Object) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:177) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:112) at com.sun.proxy.$Proxy3.getSerialAndIncrement(Unknown Source) at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:83) at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52) at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103) at java.lang.Thread.run(Thread.java:748) {noformat} I'll attach the full client and server dumps. -- This message was sent by Atlassian JIRA (v7.5.0#75005)