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

[Tim Fox (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Fox closed JBMESSAGING-1699.
--------------------------------

    Resolution: Done


We believe this issue should be fixed now.

Adrian - can you try trunk out in your setup?

You can monitor memory by using the new parameter that jeff added - this will tell you if you are running out of RAM when the problem occurs

If the problem re-occurs we will reopen the task.

> 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