Red Hat Bugzilla – Bug 1278168
[QE] (6.4.z) Server retrying remote JCA connection cannot be cleanly shut down
Last modified: 2016-12-15 09:46:41 EST
Description of problem:
We've found new issue with shutting down of EAP server retrying JCA outbound connection to remote server.
Version-Release number of selected component (if applicable):
EAP 6.4.5.CP.CR1 (HornetQ 2.3.25.SP5)
Start 1st EAP 6.4.5 with queue OutQueue
Start 2nd EAP 6.4.5 with deployed EJB which sends message to remote queue OutQueue
Call EJB to send message to remote OutQueue
Shutdown 1st server
Try to shutdown 2nd server - this never happens as it's retrying connection to 1st server and following warning is logged every 2s:
21:00:22,820 WARN [org.hornetq.core.client] (Thread-2 (HornetQ-client-global-threads-1761373667)) HQ212006: Waiting 2,000 milliseconds before next retry. RetryInterval=2,000 and multiplier=1
2nd server shutdowns.
Attaching configuration from servers, ejb and threadump from 2nd server.
Customer will not be able to cleanly shutdown server and must kill it.
Created attachment 1089840 [details]
Created attachment 1089841 [details]
Created attachment 1089842 [details]
Created attachment 1089843 [details]
EJB can be called by following code:
final Properties env = new Properties();
env.put(Context.PROVIDER_URL, String.format("%s%s:%s", "remote://", "127.0.0.1", 4447));
Context ctx = new InitialContext(env);
SimpleSendEJB simpleSendEJB = (SimpleSendEJB) ctx.lookup("ejb-sender/SimpleSendEJBBean!org.jboss.qa.hornetq.apps.ejb.SimpleSendEJB");
Created attachment 1091753 [details]
Client Application to Invoke EJB
I have also been able to reproduce this issue on EAP 6.4.4 (HornetQ 2.3.25.SP3). So this does not appear to be a regression.
*** This bug has been marked as a duplicate of bug 1301969 ***