Hi Tim,
Just to clarify.
The issue is not that the "callback/delayed" message is not part of the
transaction.
The issue is that the actual enqueuing of the message with
AMQ_SCHEDULED_DELAY is not part of the ambient transaction.
Hope this clarifies our problem.
Regards
John
--
View this messa
On Fri, 2012-10-26 at 17:41 -0700, arkin wrote:
> I have observed that when sending delayed delivery messages (with
> AMQ_SCHEDULED_DELAY values in the header), ActiveMQ does not seem to be
> including the delivery in the original transaction. This results in
> duplicate messages being delivered i
I have observed that when sending delayed delivery messages (with
AMQ_SCHEDULED_DELAY values in the header), ActiveMQ does not seem to be
including the delivery in the original transaction. This results in
duplicate messages being delivered in my setup. Here is how I tested:
1. Send a message to a
