The same with any ack mode in JMS.
As long as you don't close the session, delivered but not acked messages will remain dequeued until the session is closed.
this is my first JMS queue experience so forgive my newb questions but maybe you could help me understand the following scenario....
I have a server java app with 200 threads running, each thread has dequeued an item to work on. Something happens to the server and it crashes while in progress. When it restarts up and re-connects to hornet with a brand new process will it get the same 200 it was working on before? will they be pushed to the back of the queue? Will hornet detect a connection from the same host and try and re-establish the old session?
I guess my basic question that I didn't see in the docs is... what happens when my client app crashes while dequeing?
When connection-ttl is hit, the server side resources for the failed client will be cleaned up resulting in unacknowledged messages being put back on the queue.
doh, that was the link I was looking for
not sure this is working correctly, I'm posting a new thread on the subject