Setting timeout property to non-zero value in the remoting-bisocket-service.xml file stops JBoss Messaging working properly

Solution Unverified - Updated -

Issue

  • It is difficult to describe precisly the symptoms of this issue because it will depends on the version of JBoss EAP, JBoss Remoting and JBoss Messaging. Each combination may display different symptoms.
  • But in general if timeout property in remoting-bisocket-service.xml is set to non-zero value a JBoss Messaging client would consume messages out of order, consume only some of the messages or stop consuming messages after first  message. Message producers are not being affected.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 4.3 CP05 or greater (4.3 CP04 does not have this problem)
    • 5.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.