Inactivity monitor does not time out on stuck socket writes in ActiveMQ
Issue
We see JMS clients stuck in a socket write but the inactivity monitor does not seem to time out although no data gets exchanged between broker and client. Those connections should get closed by the inactivity monitor in order to free broker resources but instead they remain open for indefinite.
Environment
- JBoss A-MQ 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.