You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2008/12/03 00:57:05 UTC
[jira] Assigned: (AMQ-2015) Deadlock in activemq, seems to occur on
startup when clients are attempting to connect
[ https://issues.apache.org/activemq/browse/AMQ-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-2015:
-------------------------------
Assignee: Rob Davies
> Deadlock in activemq, seems to occur on startup when clients are attempting to connect
> --------------------------------------------------------------------------------------
>
> Key: AMQ-2015
> URL: https://issues.apache.org/activemq/browse/AMQ-2015
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.2.0
> Environment: ubunutu linux, xen instance with two cores
> Linux amq01 2.6.24-21-xen #1 SMP Wed Oct 22 01:07:57 UTC 2008 x86_64 GNU/Linux
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
> Reporter: Nicholas Hanssens
> Assignee: Rob Davies
> Attachments: activemq.xml, adump
>
>
> This seems to happen when I start up the instance up and clients are attempting to connect (e.g. after a live restart)...though I cannot consistently verify that.
> It gets into a deadlock state. If I look at the queues on the web monitor, it shows that only one has been created (of the ~30 that the connecting clients will attempt to recreate). Connections are being opened both over openwire (about 30) and stomp+ssl( a few hundred).
> Thread dump and a copy of activemq.xml is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.