[ http://jira.jboss.com/jira/browse/JBMESSAGING-1159?page=comments#action_1... ] Tim Fox commented on JBMESSAGING-1159: -------------------------------------- Hi Travis- I notice you're using Spring. Have you seen this wiki page (from the JBM FAQ) about using Spring with JBM? http://wiki.jboss.org/wiki/Wiki.jsp?page=JBMSpringJMSTemplateNotes (BTW You should use your support account for the best response times.) -- 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-1159?page=comments#action_1... ] Tim Fox commented on JBMESSAGING-1159: -------------------------------------- I can see from your stack that you're using Spring DefaultMessageListener container. I would be *very* careful so you don't lose messages (see http://www.jboss.org/index.html?module=bb&op=viewtopic&t=123433 - not the part about SQL) Well.. sometimes you may be lucky :) But I wouldn't bet on it. If we have other higher priority stuff to do, the forums might go for days/weeks without us answering them. Regarding the issue at hand: I can see why the deadlock is occuring. We have a scheduled delivery timing out and delivering a message. This tries to obtain locks on the ClusterRoundRobinDistributor and Channel in that order Concurrently you have a non scheduled delivery occurring. This is attempting to obtain locks on Channel and ClusterRoundRobinDistributor in that order. Hence the deadlock. I notice you are using a snapshot - so instability is expected. The fix for this should be fairly straightforward. I'll make sure it goes into the SP2 release which should happen shortly. -- 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-1159?page=all ] Tim Fox closed JBMESSAGING-1159. -------------------------------- Resolution: Done -- 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