MDBs are slowly dying in JBoss EAP
Issue
Over the past five days we have a situation where all available MDBs for a queue are slowly dying off until there are zero MDBs left consuming messages. We do not use remote queues and are only using the in-vm queues. We have made no changes to our queues nor to the MDBs that are consuming the messages. Upon a server restart the messages are handled normally, but eventually all MDBs eventually die again.
I see the following in our logs:
10:44:33,168 WARN [org.hornetq.core.server.impl.ServerSessionImpl] (hornetq-failure-check-thread) Client connection failed, clearing up resources for session 73d59519-0ff8-11e3-8db9-e3bd47286971
10:44:33,169 WARN [org.hornetq.core.server.impl.ServerSessionImpl] (hornetq-failure-check-thread) Cleared up resources for session 73d59519-0ff8-11e3-8db9-e3bd47286971
10:44:33,169 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] (hornetq-failure-check-thread) Connection failure has been detected: 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=3]
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
