You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2008/03/25 00:43:32 UTC

[jira] Commented: (AMQ-1092) Deadlock when ActiveMQ 4.X is run as an embedded broker inside JBoss 4.X with "vm://localhost" configured in the ra.xml file.

    [ https://issues.apache.org/activemq/browse/AMQ-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41774#action_41774 ] 

David Jencks commented on AMQ-1092:
-----------------------------------

A possibly related problem was fixed in AMQ-1438.

> 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.0.1, 4.0.2, 4.1.0
>         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
>             Fix For: 5.0.0
>
>         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.
-
You can reply to this email to add a comment to the issue online.