[ http://jira.jboss.com/jira/browse/JBMESSAGING-546?page=comments#action_12... ] Ovidiu Feodorov commented on JBMESSAGING-546: --------------------------------------------- Deadlock: 2006-09-18 22:06:46,109 6281 TRACE [org.jboss.jms.server.container.ServerLogInterceptor] @main invoking ConsumerAdvised->ConsumerEndpoint[-2147483626].close() 2006-09-18 22:06:46,109 6281 TRACE [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] @Thread-3 ConsumerEndpoint[-2147483626] receives Reference[1537]:RELIABLE for delivery The main thread tries to close the ConsumerEndpoint, grabs ConsumerEndpoint's main lock and gets stuck trying to get Channel->Router->receivers' lock, in process of removing the ConsumerEndpoint from the channel. Thread-3 has Channel->Router->receivers' lock and gets stuck trying to grab ConsumerEndpoint's main lock. -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-546?page=comments#action_12... ] Ovidiu Feodorov commented on JBMESSAGING-546: --------------------------------------------- Increased tracing resolution. -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-546?page=comments#action_12... ] Ovidiu Feodorov commented on JBMESSAGING-546: --------------------------------------------- the code should contain sufficient trace statements to identify and fix the deadlock, when it occurs. -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-546?page=comments#action_12... ] Ovidiu Feodorov commented on JBMESSAGING-546: --------------------------------------------- Can't get it to repeat, with the new tracing code. Repeat it in a loop. -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-546?page=comments#action_12... ] Ovidiu Feodorov commented on JBMESSAGING-546: --------------------------------------------- The main thread grabs ServerConsumerEndpoint's main lock in ServerConsumerEndpoint.close() and tries to remove itself from the channel's router. Cannot do that because Thread-3 holds the router's lock. Thread-3 delivers a new reference to ServerConsumerEndpoint while holding the router's lock (unnecessarily), and tries to grab ServerConsumerEndpoint's main lock, which is unavailable. The deadlock was fixed by reducing the time Thread-3 holds the router's lock. -- 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