We have several JMS-driven standalone 24x7 applications used with FUSE Message Broker 184.108.40.206.
All of applications works fine, except one - periodically it stops receiving new messages. This "stop" has very strange nature - no logs, no errors - nothing. After that "silent stop" we usually restarts this application and it always hang's on method consumer.close() - then we just kill the JVM-process.
This problematic application has one distinctive feature - it is the leader among all our JMS-driven applications on the number of produced/consumed JMS-messages.
Currenly this application "lives" 2-3 days, others - months.
Can anybody helps to find source of this strange behaviour?
All our JMS-applications use this JMS-specific options:
- Message listeners with AUTO_ACKNOWLEDGE (default onMessage)
- transport type - tcp
- wireFormat.maxInactivityDuration = 0
- soTimeout = 0
Problem was found - it was a deadlock in third-pary library (ehcache 1.5).
This thread can be removed.