Ack now or too lat - weird behaviour of transaction on ActiveMQ over stomp
I use stomp (1.2) to connect to ActiveMQ (5.15). It is a Python client and stomp.py library is employed. A transaction begins when one message is received, the client does some processing then acknowledge the message, then commit the transaction. Such loop starts over when a new message is received.
There is a scenario where I found the problem. There could be more then one messages are received before the transaction begin-process-ack-commit loop. And such loops handle only one message in one go. What is the issue? The second message received earlier will not be acknowledged at all.
This message contains confidential information and is intended only for the individual(s) addressed in the message.
If you are not the named addressee, you should not disseminate, distribute, or copy this e-mail.
If you are not the intended recipient, you are notified that disclosing, distributing, or copying this e-mail is strictly prohibited.
Re: Ack now or too lat - weird behaviour of transaction on ActiveMQ over stomp
Then this sounds like a bug. Can you please submit a bug for it in JIRA? If
possible, please attach your actual code that reproduces the problem, in
case whoever implements the fix has trouble reproducing it.