Hello All,
Please cast your vote on this thread to release RC1 as the
official Qpid Dispatch Router version 1.13.0.
RC1 of Qpid Dispatch Router version 1.13.0 can be found here:
https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.13.0-rc1/
It is tagged as 1.13.0-rc1.
The JIRAs
Hi Timothy,
I just synced that change and verified that it fixes the issue in my test setup.
Thanks for the quick turnaround! __
-Timo
On 8/12/20, 8:38 AM, "Timothy Bish" wrote:
On 8/10/20 5:05 PM, Timo Naroska wrote:
> Hi,
>
> we're seeing sporadic cases in our JMS
On 8/10/20 5:05 PM, Timo Naroska wrote:
Hi,
we're seeing sporadic cases in our JMS application where the
AmqpTransferTagGenerator used inside JMS MessageProducer is sending duplicate
delivery-tags. This leads to the producer being closed and unusable for any
further operations.
Setup:
The client should probably discard the delivery tag associated with a
failed send when a timeout occurs rather than return it to the tag
pool, as it indeed wont know the other side isnt done with it, and
certainly it shouldnt be used immediately on the next sends. That or
kill the producer itself
Can you answer my question from before: Are you actually looking for
your queue and address names to differ?
I'm not convinced the client address string you gave will necessarily
do what your mail suggests you want (consuming from a queue named
Test). However I am also not entirely clear on what
Thanks for your reply Gordon.
I have tried to update in ActiveMQ broker.xml, Queue created with specified
max consumer count.
After running consumer with Filter "X", successfully able to listen the
Queue with filter X.
Tried to run the second consumer with Filter "Y", Failed got QPID client
