[jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1701) Server closes connections from alive clients

[Bijith Kumar (JIRA)]

Server closes connections from alive clients
--------------------------------------------

                 Key: JBMESSAGING-1701
                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1701
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 2.0.0.beta4
         Environment: Windows Vista-32 bit
            Reporter: Bijith Kumar
            Assignee: Tim Fox
            Priority: Critical
         Attachments: Sender.java

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 (e.g. just looping in an empty while loop). It seems this pinging is not happening always. Because, in my case, client program sends some messages and sits idle for 5 min and server closes the connection after 2-3 minutes saying "no ping received". Please see the complete 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.rem
oting.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 be
tween 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.ser
ver.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.ser
ver.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.rem
oting.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 be
tween 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.ser
ver.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.ser
ver.impl.ServerSessionImpl]  Cleared up resources for session 4dae6b96-81ba-11de-93a5-001a	

Attached is the simple JMS client class to reproduce the issue. It sends 5000 messages to the Queue and idles for 5 minutes (just loops in an empty while loop) before exiting. Please find test instructions below.
1) Update JMX_URL, HOST  and PORT in the attached Sender.java file according to your env
2) Compile and execute Sender.java a couple of times
3) Observe that the Server closes connection after 2-3 minutes printing WARNING messages shown above. If you are not able to reproduce it this way, try sending more messages so that paging starts in server, that would definitely reproduce it. I was able to reproduce the issue both ways (i.e. paged or not paged).


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira