- "Tom Samplonius" <[EMAIL PROTECTED]> wrote:
> I noticed some strange behavior with ActiveMQ 4.1.1 and the Stomp
> protocol. When I connect, I set the ack mode to "client". I read a
> message, and exit. Since I did not ack the message, I should expect
> to get the same message on next exec
I noticed some strange behavior with ActiveMQ 4.1.1 and the Stomp protocol.
When I connect, I set the ack mode to "client". I read a message, and exit.
Since I did not ack the message, I should expect to get the same message on
next execution, and I do, as long as I do an explicit disconne
