MDB disconnects from a destination periodically

Issue

• Under very heavy load MDBs can be disconnected from a destination.
  Sample log entry that

WARN  [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

• On SOA-P We get warnings from JON indicating the HornetQ Connection Manager is down. We also see Unresponsive EPR messages from ERP using ConnectionFactory to connect to a Queue. That Queue also shows there are many unconsumed messages on the related queue, queue/CallbackQueue.

   INFO  [org.jboss.soa.esb.client.ServiceInvoker] (pool-77-thread-68) Unresponsive EPR: JMSEpr [ PortReference < <wsa:Address jms:192.168.1.2:1099#queue/CallbackQueue></wsa:Address>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 192.168.1.2:1099></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:destination-type : queue></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:destination-name : queue/CallbackQueue></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:persistent : true></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:transacted : false></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms></wsa:ReferenceProperties> > ] for message: header: [ To: EPR: PortReference < <wsa:Address logical:JBossESB-Internal#JBpmCallbackService></wsa:Address>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/logical></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:jbpmTokenId : 25138613></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:jbpmNodeId : 24494847></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:jbpmProcessInstId : 25138612></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:jbpmProcessNodeVersionCounter24494847_25138613 : 0></wsa:ReferenceProperties> > From: InVMEpr [ PortReference < <wsa:Address invm://536d61727463617264242424242424242424242424557064617465536d6172746361726444657461696c734261636b656e64/false?false#10000></wsa:Address>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/invm></wsa:ReferenceProperties>, <wsa:ReferenceProperties jbossesb:passByValue : false></wsa:ReferenceProperties> > ] RelatesTo: 83f135a2-147b-4587-a31e-fffbea06a6c6 ]

• On EAP We have a single application which continually sends messages to the jms queue to be processed by an MDB (also in the same EAR) Connection lookup is done via the the InVmConnectionFactory and we always clean up all the resources in a finally block after sending to the queue.

  • MDB Stops listening after sometime. In our customer we have seen at our MDB stops listening after sometime. this is happening quiet often.