Bug 65305 - JMS Subscriber infinite loop
Summary: JMS Subscriber infinite loop
Status: NEEDINFO
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.4.1
Hardware: All Linux
: P2 critical (vote)
Target Milestone: JMETER_5.5
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-14 11:48 UTC by alessiogiovanni.baroni
Modified: 2021-06-06 13:24 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description alessiogiovanni.baroni 2021-05-14 11:48:55 UTC
With an up and running but empty queue on ActiveMQ Artemis broker the JMS Subscriber loops indefinitely although I have 1 thread with 1 loop count.

If I enclose the JMS Subscriber within a Runtime Controller with a strictly positive Runtime (seconds) the behaviour doesn't change.
Comment 1 alessiogiovanni.baroni 2021-05-14 11:52:27 UTC
With a TRACE level there is this message forever:

2021-05-14 13:40:27,330 TRACE o.a.a.a.c.p.c.i.ChannelImpl: RemotingConnectionID=3804381c Writing buffer for channelID=11
2021-05-14 13:40:27,332 TRACE o.a.a.a.c.p.c.i.RemotingConnectionImpl: RemotingConnectionID=3804381c handling packet PACKET(SessionReceiveMessage)[type=75, channelID=11, responseAsync=false, requiresResponse=false, correlationID=-1, packetObject=SessionReceiveMessage, message=ClientMessageImpl[messageID=707152, durable=false, address=Test,userID=null,properties=TypedProperties[_hornetq.forced.delivery.seq=699]], consumerID=0, deliveryCount=0]
2021-05-14 13:40:27,332 TRACE o.a.a.a.c.c.i.ClientConsumerImpl: org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@66e64f6e{consumerContext=ActiveMQConsumerContext{id=0}, queueName=Test}::There was nothing on the queue, leaving it now:: returning null
2021-05-14 13:40:27,332 TRACE o.a.a.a.c.c.i.ClientConsumerImpl: org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@66e64f6e{consumerContext=ActiveMQConsumerContext{id=0}, queueName=Test}:: returning null
2021-05-14 13:40:27,332 TRACE o.a.a.a.c.c.i.ClientConsumerImpl: org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@66e64f6e{consumerContext=ActiveMQConsumerContext{id=0}, queueName=Test}:: receive(500)
2021-05-14 13:40:27,332 TRACE o.a.a.a.c.c.i.ClientConsumerImpl: org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@66e64f6e{consumerContext=ActiveMQConsumerContext{id=0}, queueName=Test}::receive(500, false)
2021-05-14 13:40:27,832 TRACE o.a.a.a.c.c.i.ClientConsumerImpl: org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@66e64f6e{consumerContext=ActiveMQConsumerContext{id=0}, queueName=Test}::Returning null
2021-05-14 13:40:27,832 TRACE o.a.a.a.c.c.i.ClientConsumerImpl: org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@66e64f6e{consumerContext=ActiveMQConsumerContext{id=0}, queueName=Test}:: receive(500) -> null, trying again with receive(0)
2021-05-14 13:40:27,832 TRACE o.a.a.a.c.c.i.ClientConsumerImpl: org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@66e64f6e{consumerContext=ActiveMQConsumerContext{id=0}, queueName=Test}::receive(0, true)
2021-05-14 13:40:27,833 TRACE o.a.a.a.c.c.i.ClientConsumerImpl: org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@66e64f6e{consumerContext=ActiveMQConsumerContext{id=0}, queueName=Test}::Forcing delivery
2021-05-14 13:40:27,833 TRACE o.a.a.a.c.p.c.i.ChannelImpl: RemotingConnectionID=3804381c Sending packet nonblocking PACKET(SessionForceConsumerDelivery)[type=78, channelID=11, responseAsync=false, requiresResponse=false, correlationID=-1, packetObject=SessionForceConsumerDelivery, consumerID=0, sequence=700] on channelID=11
Comment 2 Felix Schumacher 2021-06-06 13:24:02 UTC
Can you provide a minimal test plan to reproduce?

Have you set up a timeout value on the sampler?