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

Alex Rudyy updated QPIDJMS-242:
-------------------------------
    Attachment: broker-log.snippet.txt

> Creation of consumer hangs when connection is in a process of re-establishing 
> by failover
> -----------------------------------------------------------------------------------------
>
>                 Key: QPIDJMS-242
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-242
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.11.1, 0.20.0
>         Environment: Qpid Broker 7.0.0-SNAPSHOT
>            Reporter: Alex Rudyy
>         Attachments: ConsumerCreationHangsOnFailover.java, 
> broker-log.snippet.txt, thread-dump.txt
>
>
> The creation of consumer (Session#createConsumer) hangs if invoked when 
> underlying connection is being re-established by failover process. Even when 
> failover successfully restores the connectivity, the invoked method 
> createConsumer  does not return. I see the following in the stack trace:
> {noformat}
> "main" prio=10 tid=0x00007f2524009800 nid=0x3d5d waiting on condition 
> [0x00007f252b0e4000]
>    java.lang.Thread.State: WAITING (parking)
>       at sun.misc.Unsafe.park(Native Method)
>       - parking to wait for  <0x00000007ad360b30> (a 
> java.util.concurrent.CountDownLatch$Sync)
>       at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>       at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>       at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>       at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
>       at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
>       at 
> org.apache.qpid.jms.provider.ProviderFuture.sync(ProviderFuture.java:97)
>       at 
> org.apache.qpid.jms.JmsConnection.createResource(JmsConnection.java:601)
>       at 
> org.apache.qpid.jms.JmsConnection.createResource(JmsConnection.java:590)
>       at 
> org.apache.qpid.jms.JmsMessageConsumer.<init>(JmsMessageConsumer.java:114)
>       at 
> org.apache.qpid.jms.JmsMessageConsumer.<init>(JmsMessageConsumer.java:72)
>       at org.apache.qpid.jms.JmsSession.createConsumer(JmsSession.java:387)
>       at org.apache.qpid.jms.JmsSession.createConsumer(JmsSession.java:375)
>       at org.apache.qpid.jms.JmsSession.createConsumer(JmsSession.java:367)
>       at org.apache.qpid.jms.example.Test2.main(Test2.java:65)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>       at java.lang.reflect.Method.invoke(Method.java:606)
>       at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> {noformat}
> The consumer is created successfully on broker side. Broker even sends the 
> messages through.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to