[ https://issues.apache.org/activemq/browse/AMQ-1092?page=comments#action_37677 ] Luis A Lopez-Rivera commented on AMQ-1092: ------------------------------------------
Additional information: Tests are with XA Transactions. > Deadlock when ActiveMQ 4.X is run as an embedded broker inside JBoss 4.X with > "<config-property-value>vm://localhost</config-property-value>" configured in > the ra.xml file. > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: AMQ-1092 > URL: https://issues.apache.org/activemq/browse/AMQ-1092 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 4.1.0, 4.0.1, 4.0.2 > Environment: Tested OSes: Windows 2000 Pro, Window XP Pro x64, Linux > Java: 1.5 SDK & 1.4 SDK > J2EE Server: JBoss 4.03.S1 & 4.0.4GA > Reporter: Luis A Lopez-Rivera > Attachments: deadlock.txt, javastack.txt > > > Deadlock occurs when ActiveMQ 4.X is run as an embedded broker inside JBoss > 4.X with "<config-property-value>vm://localhost</config-property-value>" > configured in the ra.xml file. If "tcp://localhost:61616" is used instead of > "vm://localhost" then everything works fine. > The deadlock seems to occur when two messages are being handled (one is being > produced and one being consumed). If I prevent two messages from being > handled at the same time (one produced and one consumed) then the deadlock > does not occur. > This situation can be reproduced every single time tested. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
