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

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.