[
https://jira.jboss.org/jira/browse/JBMESSAGING-1699?page=com.atlassian.ji...
]
Clebert Suconic commented on JBMESSAGING-1699:
----------------------------------------------
Some relevant conversation we had on IRC:
11:57:51 AM) adrianW: clebert - this is what I did:
(11:58:00 AM) adrianW: 1. upgrade all clients to b4 (still talking to b3 server)
(11:58:11 AM) adrianW: 2. stop b3 server
(11:58:22 AM) adrianW: 3. start b4 server with same config, port
(11:58:34 AM) adrianW: 4. clients reconnect and everything now on b4
(11:58:41 AM) adrianW: 5. restart b4 server just to be sure
(11:58:55 AM) adrianW: 6. some clients did not seem to reconnect, so I restarted them
(11:59:10 AM) adrianW: at some point during 6 the crash happened
(12:00:57 PM) clebert: adrianW: ok.. I see...
(12:00:57 PM) clebert: One thing though.. until we are final (GA).. I don't think we
are guaranteeing version compatibility between the wire protocol.
(12:00:57 PM) clebert: I don' t think anything changed between Beta3 and 4.. but just
to let you know
(12:01:12 PM) adrianW: yeah, I heard that
(12:01:21 PM) adrianW: I tried it out on a test client/server first and it seemed ok
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: Tim Fox
Attachments: messaging.log.fail
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