"Tim" wrote :
| "Clebert" wrote :
| | Second point also:
| |
| | What to do when a durable subscriber gets the queue refilled?
| | - The client will probably receive the message again. I would just ignore
redeliveries.
| |
|
| I don't understand the issue here. Can you explain more?
|
The consumer is going to be recreated the same way the connection on the previous example.
(creating a new consumer / replacing the IDs on the old objects).
On that case, the new server will think it's a new client connecting and it will
resend non committed messages from a durable subscription. (So I hope).
On that case, I'm considering to ignore message previously sent, and on the list of
CurrentTransaction.ACKs(). I just want to know if this is everybody's expected
behavior.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978882#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...