[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1012) SeveralClientsStressTest leads to remoting dead lock
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1012?page=comments#action_1... ]
Clebert Suconic commented on JBMESSAGING-1012:
----------------------------------------------
Clebert - could you link it to the actual remoting issue?
This is a new remoting bug...
It has to do with createSocket.. there are no threads waiting on the notify.
I will investigate the root cause, open a new JIRA and link it here.
It wasn't clear to me from the description, but this is a
remoting issue.
The description says "remoting dead lock". So it is a remoting issue. I just
don't know what issue yet.
The symptom that I know that is the client is locked up.. but in a different point where
we used to see before.
SeveralClientsStressTest leads to remoting dead lock
----------------------------------------------------
Key: JBMESSAGING-1012
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1012
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.4.0.CR1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Critical
Fix For: 1.4.0.CR1
SeveralClientsStressTest is not working...
It looks like a racing between Timeouts and client.disconnect...
Sometimes it fails, sometimes it locks up
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira