On 14 February 2018 at 09:59, Keith W wrote:
> Hi Bryan
>
>
>> So that brings me to the potential bug. I found that when using the JMS
>> QueueBrowser it actually increments the Delivery Count for a message
>> everytime it is browsed. That is why most of my source messages had a
>> Delivery Coun
Hi Bryan
Yes, that's a defect. Thanks for reporting. From my initial
> So that brings me to the potential bug. I found that when using the JMS
> QueueBrowser it actually increments the Delivery Count for a message
> everytime it is browsed. That is why most of my source messages had a
> Deli
I think I found why this behavior was occurring but I think I might have
uncovered a bug with JMQ queue browsing...
I tested with another source queue and there were no messages were being
moved to the DLQ for that queue - the stayed on the source queue after the
connection was closed and that is
I just ran another test where I set the url to have a maxprefetch of 0:
String brokerUrl =
"amqp:///spgqpiddev?maxprefetch='0'&brokerlist='tcp://spgappdevmutil:5672'";
And it still ended up moving 2 messages to the DLQ after the connection was
stopped. I'm really confused about this behavior.
I'm using qpid-broker-j-7.0.1, qpid-jms-amqp-0-x-6.3.0 and JDK 1.8.
We have a Java app that using using a JMS MessageListener to consume message
from a Queue. Occasionally we want to stop message consumption on the
Listener and then restart it. To stop message consumption I simply call the
.sto
