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:
QPID-J 7.16 broker cluster of 3 using BDB HA rep
We are planning to start a vote on Wednesday to release Qpid Dispatch
1.13.0. Please test the master branch and report any critical issues
or regressions immediately. Code freeze is in effect until the vote
starts.
Thanks.
-
To u
On 10/08/2020 9:49 am, umohank wrote:
Thanks for your reply Robbie.
I don't want to make any change in broker.xml, just for testing purpose I
have made changes in broker.xml .
In QPID address while creating receiver do we need to set Max consumer(i.e.
to -1), so that Queue will be created and a
Sorry, it is duplicate issue.
By mistake submitted twice, I didn't find the way to delete the duplicate.
Thanks,
Mohan
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
-
To unsubscribe, e-mail: u
I had already replied before this to your initial thread with some
suggestions, see there.
I see you used Nabble, possibly it was just being slow, though the
posts are there as I look. It seems Nabble may be on the way out
though: http://support.nabble.com/The-Future-of-Nabble-td7605923.html.
You
Thanks for your reply Robbie.
I don't want to make any change in broker.xml, just for testing purpose I
have made changes in broker.xml .
In QPID address while creating receiver do we need to set Max consumer(i.e.
to -1), so that Queue will be created and any number of consumer can consume
from i
The current client can be found at
https://qpid.apache.org/components/jms/, as this ~5yr old old thread
indicates (or also, https://qpid.apache.org/maven.html and
https://qpid.apache.org/download.html). Please create new threads for
new questions.
I have updated QPID-6447 to note that it was never
Hi Team,
This is regarding qpid-amqp-1-0-client-jms library.
After the deadlock issue which is mentioned
https://issues.apache.org/jira/browse/QPID-6447 in this link.
Any new version is introduced which solves deadlock problem after 0.32
version?
If not, can you suggest any other library which is
