[
http://jira.jboss.com/jira/browse/JBMESSAGING-929?page=all ]
Tim Fox closed JBMESSAGING-929.
-------------------------------
Resolution: Done
I think it is acceptable to just rely on leasing to close dead connections.
Implement a proper fix for JBMESSAGING-928
------------------------------------------
Key: JBMESSAGING-929
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-929
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Fix For: 1.2.0.SP2, 1.0.1.SP5
We need a proper fix for JBMESSAGING-928.
I have disabled failure detection on ServerConsumerEndpoint temporarily because of the
Valve effect on readWrites/writeLocks.
When a readWrite is being promoted to writeLock.. it will probably hold other
synchronized locks what will never release the lock.. we need a proper fix to this issue.
(Maybe using async executors).
A propert testcase has to be developed.
--
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