Thanks, I got it to work.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-CPP-Rollback-function-returns-but-the-server-isn-t-done-rollbacking-tp4668896p4668925.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On 07/05/2013 09:52 AM, cineva wrote:
The test was a short version of what I'm trying to do. The following code
depends on the time it takes from the rollback to the second receive. If I
wait a while after the rollback the output is "received received" else it's
"received not received". Is this h
The test was a short version of what I'm trying to do. The following code
depends on the time it takes from the rollback to the second receive. If I
wait a while after the rollback the output is "received received" else it's
"received not received". Is this how ActiveMQ-CPP and ActiveMQ are suppose
On 07/05/2013 08:22 AM, cineva wrote:
My problem is that I expected to find "Another Test message" in the queue and
not "Test message". If for example I insert a sleep after
session->rollback(); the program runs as expected. Why does
session->rollback(); return but the session isn't exactly rollb
My problem is that I expected to find "Another Test message" in the queue and
not "Test message". If for example I insert a sleep after
session->rollback(); the program runs as expected. Why does
session->rollback(); return but the session isn't exactly rollbacked? Is
this the intended behavior?
Not entirely sure what you are trying to accomplish here. You always
commit the messages so they are going to get sent, and if you use the
default redelivery policy the messages that a consumer receives but
rolls back will get redelivered.
On 07/05/2013 03:53 AM, cineva wrote:
The following
The following program depends on the time it takes to rollback the session.
If I run it in a debugger line by line it returns the correct behavior
("Another Test message" in "testqueue" queue) but if I let it run I get
"Test message". Is this something by design (are only asynchronous rollbacks
sup
