[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-942) A deadlock encountered on ConnectionValidator
Mayank Mittal (JIRA)
jira-events at lists.jboss.org
Thu Sep 22 08:04:27 EDT 2011
[ https://issues.jboss.org/browse/JBREM-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629854#comment-12629854 ]
Mayank Mittal commented on JBREM-942:
-------------------------------------
I'm facing the same issue with
AS : JBoss 4.2.3 GA
Remoting: 2.4.0 SP1
whenever during the fail-over I perform any operation. I'm using HA-JNDI (1100) to make connections to my server. As it is expected from the HA system, that fail-over should be transparent from user point of view.
here is the stack
"Thread-113" daemon prio=10 tid=0x00007f53243ea000 nid=0x57e5 waiting for monitor entry [0x00007f5322829000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.jboss.remoting.ConnectionValidator.removeConnectionListener(ConnectionValidator.java:359)
- waiting to lock <0x00000000c7b93480> (a java.lang.Object)
at org.jboss.remoting.Client.removeConnectionListener(Client.java:445)
at org.jboss.jms.client.remoting.JMSRemotingConnection.removeConnectionListener(JMSRemotingConnection.java:533)
- locked <0x00000000c7b27a08> (a org.jboss.jms.client.remoting.JMSRemotingConnection)
at org.jboss.jms.client.container.ConnectionAspect.handleClose(ConnectionAspect.java:185)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:179)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.close(ClientConnectionDelegate.java)
at org.jboss.jms.client.JBossConnection.close(JBossConnection.java:132)
at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager$ConnectionInfo$1.call(ClusterConnectionManager.java:705)
at EDU.oswego.cs.dl.util.concurrent.FutureResult$1.run(FutureResult.java:75)
at java.lang.Thread.run(Thread.java:662)
"Timer-22" daemon prio=10 tid=0x0000000041cfd800 nid=0x5264 waiting for monitor entry [0x00007f5323234000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.jboss.remoting.ConnectionValidator.notifyListeners(ConnectionValidator.java:600)
- waiting to lock <0x00000000c7b93480> (a java.lang.Object)
at org.jboss.remoting.ConnectionValidator.access$600(ConnectionValidator.java:42)
at org.jboss.remoting.ConnectionValidator$WaitOnConnectionCheckTimerTask.run(ConnectionValidator.java:648)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
> A deadlock encountered on ConnectionValidator
> ----------------------------------------------
>
> Key: JBREM-942
> URL: https://issues.jboss.org/browse/JBREM-942
> Project: JBoss Remoting
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: transport
> Affects Versions: 2.2.2.SP5
> Environment: JBoss-EAP-4.2, JBossMessaging-1.4.0-SP3, JBossRemoting-2.2.2-SP5
> Reporter: Tyronne Wickramarathne
> Assignee: Ron Sigal
> Priority: Critical
> Fix For: 2.2.2.SP7
>
>
> This deadlock occurred on JBREM when a JBossMessaging Bridge was set and consuming messages. here's the StackTrace :
> Found one Java-level deadlock:
> =============================
> "Thread-278":
> waiting to lock monitor 0x08128544 (object 0xce8b25e0, a java.lang.Object),
> which is held by "Timer-4"
> "Timer-4":
> waiting to lock monitor 0x08129160 (object 0xce89f508, a java.util.ArrayList),
> which is held by "Thread-278"
> Java stack information for the threads listed above:
> ===================================================
> "Thread-278":
> at org.jboss.remoting.ConnectionValidator.doStop(ConnectionValidator.java:526)
> - waiting to lock <0xce8b25e0> (a java.lang.Object)
> at org.jboss.remoting.ConnectionValidator.stop(ConnectionValidator.java:252)
> at org.jboss.remoting.ConnectionValidator.removeConnectionListener(ConnectionValidator.java:344)
> - locked <0xce89f508> (a java.util.ArrayList)
> at org.jboss.remoting.Client.removeConnectionListener(Client.java:398)
> at org.jboss.jms.client.remoting.JMSRemotingConnection.removeConnectionListener(JMSRemotingConnection.java:493)
> - locked <0xce8b18c8> (a org.jboss.jms.client.remoting.JMSRemotingConnection)
> at org.jboss.jms.client.container.ConnectionAspect.handleClose(ConnectionAspect.java:184)
> at sun.reflect.GeneratedMethodAccessor134.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
> at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java)
> at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
> at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
> at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java)
> at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
> at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
> at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java)
> at org.jboss.jms.client.delegate.ClientConnectionDelegate.close(ClientConnectionDelegate.java)
> at org.jboss.jms.client.JBossConnection.close(JBossConnection.java:132)
> at org.jboss.jms.server.bridge.Bridge.cleanup(Bridge.java:1098)
> at org.jboss.jms.server.bridge.Bridge.access$1100(Bridge.java:66)
> at org.jboss.jms.server.bridge.Bridge$FailureHandler.run(Bridge.java:1496)
> at java.lang.Thread.run(Thread.java:619)
> "Timer-4":
> at org.jboss.remoting.ConnectionValidator.notifyListeners(ConnectionValidator.java:553)
> - waiting to lock <0xce89f508> (a java.util.ArrayList)
> at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:286)
> - locked <0xce8b25e0> (a java.lang.Object)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> Found 1 deadlock.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-remoting-issues
mailing list