activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (AMQ-1267) Deadlock on ServerSessionImpl that hangs all connection consumers
Date Mon, 30 Jul 2007 11:37:50 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rob Davies reassigned AMQ-1267:
-------------------------------

    Assignee: Rob Davies

> Deadlock on ServerSessionImpl that hangs all connection consumers
> -----------------------------------------------------------------
>
>                 Key: AMQ-1267
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1267
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.0.2
>         Environment: Java 1.5.0_11
>            Reporter: Jonas Collaros
>            Assignee: Rob Davies
>             Fix For: 5.0.0
>
>
> We are encountering regularly the deadlock mentioned below hours into program execution.
It has been correlated with the exhaustion of the JVM heap, though it is unclear if running
out of memory is a cause or consequence of this deadlock. At the least, system memory usage
seems stable otherwise. We well be taking further thread dumps of the system to try to pinpoint
which occurs first.
> Is this a known issue in AMQ 4.0.2, or do you have any other insights?
> Found one Java-level deadlock:
> =============================
> "Thread-20":
>   waiting to lock monitor 0x5f80a2bc (object 0x73145af0, a java.lang.Object),
>   which is held by "Thread-18"
> "Thread-18":
>   waiting to lock monitor 0x5f80a27c (object 0x73124630, a org.apache.activemq.ra.ServerSessionPoolImpl),
>   which is held by "Thread-20"
> Java stack information for the threads listed above:
> ===================================================
> "Thread-20":
> 	at org.apache.activemq.ra.ServerSessionImpl.start(ServerSessionImpl.java:118)
> 	- waiting to lock <0x73145af0> (a java.lang.Object)
> 	at org.apache.activemq.ra.ServerSessionPoolImpl.dispatchToSession(ServerSessionPoolImpl.java:149)
> 	at org.apache.activemq.ra.ServerSessionPoolImpl.removeFromPool(ServerSessionPoolImpl.java:176)
> 	- locked <0x73124630> (a org.apache.activemq.ra.ServerSessionPoolImpl)
> 	at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:178)
> 	- locked <0x731460e8> (a java.lang.Object)
> 	- locked <0x73145fe0> (a org.apache.activemq.ra.ServerSessionImpl)
> 	at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:291)
> 	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:732)
> 	at java.lang.Thread.run(Thread.java:595)
> "Thread-18":
> 	at org.apache.activemq.ra.ServerSessionPoolImpl.removeFromPool(ServerSessionPoolImpl.java:171)
> 	- waiting to lock <0x73124630> (a org.apache.activemq.ra.ServerSessionPoolImpl)
> 	at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:178)
> 	- locked <0x73145af0> (a java.lang.Object)
> 	- locked <0x731459e8> (a org.apache.activemq.ra.ServerSessionImpl)
> 	at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:291)
> 	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:732)
> 	at java.lang.Thread.run(Thread.java:595)
> Found 1 deadlock.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message