qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-6738) Joram test TopicSessionTest#testDurableSubscriber hangs against Java Broker when invoked a second time (qpid-jms-client 0.5.0)
Date Mon, 14 Sep 2015 17:29:46 GMT

    [ https://issues.apache.org/jira/browse/QPID-6738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743871#comment-14743871
] 

Robbie Gemmell commented on QPID-6738:
--------------------------------------

Recent changes on master (0.6.0-SNAPSHOT) already seem to have stopped the NPE occurring.
The tests complete, but report failure due to an exception, with the message indicating that
the peer sent an unknown error. Looking at a protocol trace suggests it was a somewhat poor
attempt at communicating that a send failed because the broker rejected a message without
setting a particular error to indicate why.

> Joram test TopicSessionTest#testDurableSubscriber hangs against Java Broker when invoked
a second time (qpid-jms-client 0.5.0)
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-6738
>                 URL: https://issues.apache.org/jira/browse/QPID-6738
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: qpid-java-6.0
>            Reporter: Keith Wall
>         Attachments: joramtest.log
>
>
> If I run {{org.objectweb.jtests.jms.conform.session.TopicSessionTest#testDurableSubscriber}}
twice against the Java Broker using the qpid-jms-client (0.5.0), the second invocation always
hangs with a NPE reported client side.
> {noformat}
> 015-09-14 09:20:55,862 INFO  [AmqpProvider:(2):[amqp://localhost:5672]] o.a.q.j.JmsConnection
Connection ID:berlin.local-52005-1442218854893-0:2 connected to remote Broker: amqp://localhost:5672
> 2015-09-14 09:20:55,864 DEBUG [AmqpProvider:(2):[amqp://localhost:5672]] o.a.q.j.p.a.AmqpAbstractResource
AmqpSession { ID:berlin.local-52005-1442218854893-0:2:1 } is now open:
> 2015-09-14 09:20:55,918 DEBUG [AmqpProvider:(2):[amqp://localhost:5672]] o.a.q.j.p.a.AmqpAbstractResource
AmqpConsumer { ID:berlin.local-52005-1442218854893-0:2:1:1 } is now open:
> 2015-09-14 09:20:55,924 DEBUG [AmqpProvider:(2):[amqp://localhost:5672]] o.a.q.j.p.a.AmqpAbstractResource
AmqpConsumer { ID:berlin.local-52005-1442218854893-0:2:1:2 } is now open:
> 2015-09-14 09:20:55,933 DEBUG [AmqpProvider:(2):[amqp://localhost:5672]] o.a.q.j.p.a.AmqpAbstractResource
AmqpConnection { ID:berlin.local-52005-1442218854893-0:2 } is now closed:
> 2015-09-14 09:20:55,936 DEBUG [main] o.a.q.j.u.ThreadPoolUtils Shutdown of ExecutorService:
java.util.concurrent.ThreadPoolExecutor@7b9f36c7[Terminated, pool size = 0, active threads
= 0, queued tasks = 0, completed tasks = 0] is shutdown: true and terminated: true took: 0.000
seconds.
> 2015-09-14 09:20:55,973 WARN  [AmqpProvider:(1):[amqp://localhost:5672]] o.a.q.j.p.a.AmqpProvider
Caught Exception during update processing: null
> java.lang.NullPointerException: null
>         at org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.getRemoteError(AmqpAbstractResource.java:232)
~[qpid-jms-client-0.5.0.jar:0.5.0]
>         at org.apache.qpid.jms.provider.amqp.AmqpFixedProducer.processDeliveryUpdates(AmqpFixedProducer.java:221)
~[qpid-jms-client-0.5.0.jar:0.5.0]
>         at org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:807)
[qpid-jms-client-0.5.0.jar:0.5.0]
>         at org.apache.qpid.jms.provider.amqp.AmqpProvider.access$2000(AmqpProvider.java:90)
[qpid-jms-client-0.5.0.jar:0.5.0]
>         at org.apache.qpid.jms.provider.amqp.AmqpProvider$17.run(AmqpProvider.java:707)
[qpid-jms-client-0.5.0.jar:0.5.0]
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_79]
>         at java.util.concurrent.FutureTask.run(FutureTask.java:262) [na:1.7.0_79]
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
[na:1.7.0_79]
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
[na:1.7.0_79]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[na:1.7.0_79]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[na:1.7.0_79]
>         at java.lang.Thread.run(Thread.java:745) [na:1.7.0_79]
> {noformat}
> Execute the following command twice to reproduce, having first started a Java Broker
in default configuration with HTTP basic auth enabled.
> {{mvn -f joramtests/pom.xml integration-test  -Djoramtests=qpid-jms-client -Dit.test=TopicSessionTest#testDurableSubscriber}}



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

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


Mime
View raw message