[jboss-user] [JBoss Messaging] - Server closes connection even if the Client is alive.

Hi, I am using JBM 2.0.0.BETA4. I am trying to migrate ActiveMQ to JBM in our product. But I have been hitting this issue of loosing connections regularly after sending some messages to the server. I have been debugging on this issue for a while now. Finally, today, I was able to reproduce this issue with a simple JMS sender class. The issue is that the server closes client connection and clears the resources even if the client is alive. Please see the server message below. [main] 17:49:54,850 WARNING [org.jboss.messaging.jms.server.impl.JMSServerManagerImpl] Binding for java:/XAConnectionFactory already exists | [main] 17:49:54,949 INFO [org.jboss.messaging.core.server.impl.MessagingServerImpl] JBoss Messaging Server version 2.0.0.BETA4 (maggot, 104) started | [Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:04,158 WARNING [org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl] Connection failure has been detected Did not receive p | lient. It is likely a client has exited or crashed without closing its connection, or the network between the server and client has failed. The connection will now be closed.:3 | [Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:04,163 WARNING [org.jboss.messaging.core.server.impl.ServerSessionImpl] Client connection failed, clearing up resources for session 4 | ba-11de-93a5-001aa035dde5 | [Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:04,163 WARNING [org.jboss.messaging.core.server.impl.ServerSessionImpl] Cleared up resources for session 4dd07287-81ba-11de-93a5-001a | [Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:06,414 WARNING [org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl] Connection failure has been detected Did not receive p | lient. It is likely a client has exited or crashed without closing its connection, or the network between the server and client has failed. The connection will now be closed.:3 | [Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:06,414 WARNING [org.jboss.messaging.core.server.impl.ServerSessionImpl] Client connection failed, clearing up resources for session 4 | ba-11de-93a5-001aa035dde5 | [Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:06,415 WARNING [org.jboss.messaging.core.server.impl.ServerSessionImpl] Cleared up resources for session 4dae6b96-81ba-11de-93a5-001a As per the JBM documentation, if a client is idle (i.e. not sending/receiving any message), it will automatically send "ping" packets periodically to prevent the server from closing it down. So my understanding is that, the server should not close the connection as long as client program is running (even though it is not sending/receiving any messages). Please confirm. If yes, It seems this pinging is not happening always. Because, in my case, client program is sitting idle for 5 min after sending some messages and after 2-3 minutes, server closes the connection saying "no ping received". Please find the test class and instructions in JIRA - https://jira.jboss.org/jira/browse/JBMESSAGING-1701 Thanks Bijith View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248126#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...