Yes.
We should not barf if an ack is received and the message can't be found.
Actually this is valid even without failover.
In general any invocation can fail as the response is being written to the caller, but
after the actual deed has been done on the server, this applies to sends as well as acks.
In the case of sends this means the call to invoke() throws an exception but the message
has actually reached the queue, in which case you don't know whether to retry or not
since you don't want duplicate messages in the queue. This is where duplicate message
detection becomes useful.
In the case of an ack it is always safe to retry the ack, *as long* as the server silently
ignores the ack if the message can't be found. If we're not doing that already we
should.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010273#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...