I'm reposting this with updated information.I'm setup to use durable Topics with retroactive=true. My application consumes messages, which lights up certain status indicators. While this works fine, I have a problem in that if the user exits and restarts my application, sometimes the messages are redelivered and sometimes they are not. I always want all non-expired messages to be redelivered upon relaunch, no matter how many times the app is relaunched, but this behavior is inconsistent. If redelivery NEVER occurs, I'd look at this as a configuration mistake, but redelivery does occur about 50% of the time. I cannot figure out why this is inconsistent. Does anyone have ideas of what I can try? I'm using 5.14.2. Might there be a way, programmatically, for the app to *manually* request a redelivery of all unexpired messages (in the order of creation), say, through a "refresh" button -- even if they have been previously consumed? Mark
-- View this message in context: http://activemq.2283324.n4.nabble.com/Redelivery-of-messages-previously-consumed-tp4721929.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
