oh wow! that worked beautifully! at first i was trying to deal with
messages that had already been paged in, but then i realized that anything
which has not yet been consumed should still be in the store. so it really
was as simple as passing a MessageRecoveryListener to the store and I can
brow
Unfortunately it is a bit convoluted to do this right now as you need
to get access to the SSLSocket that is part of the connection which
isn't exposed through the API so you need to use reflection to get
access to the Socket. But the following is an example that should
work:
ActiveMQConn
The transaction you are referring to is a transaction on the KahaDB
index and a new one will be created by KahaDB when calling that method
so you don't need to worry about it. In terms of statefulness, you
are correct that the order index tracks state of where it left off.
But I believe it is safe
