I agree. And thanks for paraphrasing me - you are right, I was thinking "AMQ is not a database" or "AMQ is not a message store" - to quote Jeff Genender who helped me to see that light.
Sounds like logging the full message content is the best approach. Once a fix is created, a new message with identical content can be injected back into the stream. Is that feasible for your use-case Rural? -- View this message in context: http://activemq.2283324.n4.nabble.com/Several-hundred-messages-occupies-almost-30G-storage-tp4692193p4692581.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
