11:31 a.m.
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.4.0.SP1
Need to investigate
--
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
11:39 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Anil Saldhana updated JBMESSAGING-1099:
---------------------------------------
Priority: Critical (was: Major)
I have to make this issue "Critical" because I have seen the case when JMS
destination authorization fails, the server just hangs.
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Tim Fox
Priority: Critical
Fix For: 1.4.0.SP1
Need to investigate
--
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
11:51 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1099:
--------------------------------------
If you can replicate this, please add instructions to this task.
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Tim Fox
Priority: Critical
Fix For: 1.4.0.SP1
Need to investigate
--
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
10:49 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Clebert Suconic updated JBMESSAGING-1099:
-----------------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120411 (was:
http://www.jboss.com/index.html?module=bb&op=viewforum&f=153)
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Tim Fox
Priority: Critical
Fix For: 1.4.0.SP1
Need to investigate
--
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
9:22 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Clebert Suconic reassigned JBMESSAGING-1099:
--------------------------------------------
Assignee: Clebert Suconic (was: Tim Fox)
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: AS 5.0 Integration
Need to investigate
--
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
9:22 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Clebert Suconic updated JBMESSAGING-1099:
-----------------------------------------
Fix Version/s: AS 5.0 Integration
(was: 1.4.0.SP1)
Affects Version/s: (was: 1.4.0.GA)
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: AS 5.0 Integration
Need to investigate
--
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
9:26 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Clebert Suconic closed JBMESSAGING-1099.
----------------------------------------
Resolution: Rejected
After investigations this became a JBAS code... we opened JBAS-4886 for this.
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: AS 5.0 Integration
Need to investigate
--
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
11:59 a.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Clebert Suconic reopened JBMESSAGING-1099:
------------------------------------------
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: 1.4.0.SP1
Need to investigate
--
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
11:59 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Clebert Suconic updated JBMESSAGING-1099:
-----------------------------------------
Fix Version/s: 1.4.0.SP1
(was: AS 5.0 Integration)
Affects Version/s: 1.4.0.GA
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: 1.4.0.SP1
Need to investigate
--
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
12:22 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Clebert Suconic closed JBMESSAGING-1099.
----------------------------------------
Resolution: Done
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: 1.4.0.SP1
Need to investigate
--
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
5:03 a.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Tim Fox reopened JBMESSAGING-1099:
----------------------------------
I am re-opening because Clebert's fix to ConsumerAspect is wrong and breaks failover.
Try running MergeQueueTest a few times to see it fail.
The problem with the fix is that it always closes the ClientConsumer in a finally block.
For failover a MessagingNetworkFailed exception would be thrown, and failover would
eventually retry after failover.
But by then the ClientConsumer had been closed.
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: 1.4.0.SP1
Need to investigate
--
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
5:09 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Tim Fox updated JBMESSAGING-1099:
---------------------------------
Fix Version/s: AS 5.0 Integration
(was: 1.4.0.SP1)
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: AS 5.0 Integration
Need to investigate
--
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
3:11 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1099:
--------------------------------------
I have temporarily commented out ConnectionConsumerTest::testStopWhileProcessing since it
hangs the test suite until this task is complete.
Be sure to uncommented it before closing this task
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: AS 5.0 Integration
Need to investigate
--
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
6:12 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1099:
--------------------------------------
ClusteredClientCrashTest also fails because of this
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: 1.4.0.SP1
Need to investigate
--
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
6:12 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Tim Fox updated JBMESSAGING-1099:
---------------------------------
Fix Version/s: 1.4.0.SP1
(was: AS 5.0 Integration)
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: 1.4.0.SP1
Need to investigate
--
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
8:09 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Tim Fox updated JBMESSAGING-1099:
---------------------------------
Fix Version/s: AS 5.0 Integration
EAP 4.3 Integration
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
Need to investigate
--
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
8:09 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1099:
--------------------------------------
I have commented out ClusteredClientCrashTest until this task is fixed
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
Need to investigate
--
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
8:09 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Tim Fox updated JBMESSAGING-1099:
---------------------------------
Priority: Blocker (was: Critical)
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
Need to investigate
--
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
12:10 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Clebert Suconic updated JBMESSAGING-1099:
-----------------------------------------
Description:
When the serverShutdown is happening on an MDB Container, handleClosing might be
interrupted by an exception what will cause the ConnectionConsumer to hang.
HandleClosing might fail because the ServerPeer is already is shutdown mode, or because
the remote server was killed already.
was:Need to investigate
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
When the serverShutdown is happening on an MDB Container, handleClosing might be
interrupted by an exception what will cause the ConnectionConsumer to hang.
HandleClosing might fail because the ServerPeer is already is shutdown mode, or because
the remote server was killed already.
--
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
11:27 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Clebert Suconic closed JBMESSAGING-1099.
----------------------------------------
Resolution: Done
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: 1.4.0.SP1, AS 5.0 Integration, EAP 4.3 Integration
When the serverShutdown is happening on an MDB Container, handleClosing might be
interrupted by an exception what will cause the ConnectionConsumer to hang.
HandleClosing might fail because the ServerPeer is already is shutdown mode, or because
the remote server was killed already.
--
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
11:31 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_1... ]
Clebert Suconic commented on JBMESSAGING-1099:
----------------------------------------------
The failure on ClusteredClientCrashTest is another case
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
When the serverShutdown is happening on an MDB Container, handleClosing might be
interrupted by an exception what will cause the ConnectionConsumer to hang.
HandleClosing might fail because the ServerPeer is already is shutdown mode, or because
the remote server was killed already.
--
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
4:25 p.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Tim Fox reopened JBMESSAGING-1099:
----------------------------------
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: AS 5.0 Integration, EAP/SOA-P Integration, 1.4.0.SP1
When the serverShutdown is happening on an MDB Container, handleClosing might be
interrupted by an exception what will cause the ConnectionConsumer to hang.
HandleClosing might fail because the ServerPeer is already is shutdown mode, or because
the remote server was killed already.
--
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
4:25 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1099) Potential deadlock in shutting down server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]
Tim Fox closed JBMESSAGING-1099.
--------------------------------
Fix Version/s: (was: AS 5.0 Integration)
(was: EAP/SOA-P Integration)
Resolution: Done
Potential deadlock in shutting down server
------------------------------------------
Key: JBMESSAGING-1099
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: 1.4.0.SP1
When the serverShutdown is happening on an MDB Container, handleClosing might be
interrupted by an exception what will cause the ConnectionConsumer to hang.
HandleClosing might fail because the ServerPeer is already is shutdown mode, or because
the remote server was killed already.
--
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
6170
days inactive
6305
days old
22 comments
3 participants
participants (3)
-
Anil Saldhana (JIRA) -
Clebert Suconic (JIRA)
-
Tim Fox (JIRA)