[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1699) Server fails with message "Did not receive initial ping for connection"

[Adrian Woodhead (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12480753#action_12480753 ] 

Adrian Woodhead commented on JBMESSAGING-1699:
----------------------------------------------

In the client logs at the same time we saw the following:

2009-08-13 16:22:33] ERROR (fm.last.jms.JMSReceiver:34) - Error connecting RECEIVER for /topic/connectionControl connected
javax.jms.JMSException: Timed out waiting for response when sending packet 30
        at org.jboss.messaging.core.remoting.impl.ChannelImpl.sendBlocking(ChannelImpl.java:312)
        at org.jboss.messaging.core.client.impl.ConnectionManagerImpl.createSession(ConnectionManagerImpl.java:326)
        at org.jboss.messaging.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:977)
        at org.jboss.messaging.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:721)
        at org.jboss.messaging.jms.client.JBossConnection.authorize(JBossConnection.java:519)
        at org.jboss.messaging.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:535)
        at org.jboss.messaging.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:115)
        at org.jboss.messaging.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:110)
        at fm.last.jms.BaseJMSObject.connect(BaseJMSObject.java:82)
        at fm.last.jms.JMSReceiver.connect(JMSReceiver.java:27)
        at fm.last.jms.ConnectionMonitor.run(ConnectionMonitor.java:48)
Caused by: MessagingException[errorCode=3 message=Timed out waiting for response when sending packet 30]
        ... 11 more
[2009-08-13 16:22:33] WARN (fm.last.jms.ConnectionMonitor:53) - Connection down, trying again in 10000ms...
[2009-08-13 16:22:36] WARN (fm.last.jms.QueueingProducer:86) - JMS connection down, dropping 10 messages (/topic/connectionControl)
13-Aug-2009 16:22:39 org.jboss.messaging.core.logging.Logger warn
WARNING: I'm closing a connection you left open. Please make sure you close all connections explicitly before letting them go out of scope!
13-Aug-2009 16:22:39 org.jboss.messaging.core.logging.Logger warn

Interesting that for some reason it looks like the client connections weren't closed - when onException is called the first thing I do is a disconnect which closes the connection.

> Server fails with message "Did not receive initial ping for connection"
> -----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1699
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1699
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 2.0.0.beta4
>            Reporter: Adrian Woodhead
>            Assignee: Jeff Mesnil
>             Fix For: 2.0.0.beta5
>
>         Attachments: jbm-jstack-fail.txt, messaging.log.0.initial_ping1.FINE, messaging.log.fail, transaudiostreamer.log.initping
>
>
> I just upgraded to 2.0.0.BETA3 to 2.0.0.BETA4. After doing the upgrade I restarted some of the JBM clients. Some of these were deadlocked and had to be stopped using "kill -9" - i.e. they did not cleanly shutdown their jbm-related resources. This went fine for about 10 clients, but at some point during this process the server went absolutely nuts, logging hundreds of messages like:
> [Thread-3 (group:JBM-scheduled-threads-1321312491)] 16:31:36,436 WARNING [org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl]  Connection failure has been detected Did not receive ping from client. 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
> There were also a number of exceptions in the server log.  After this I couldn't CTRL-C to stop the server but had to kill -9 the jbm process as it had locked up entirely.

-- 
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