Where in your configuration have you tried to implement your third requirement?
And more importantly, what makes you think it's the right requirement? If a producer sends a single message that is invalid or that hits a bug in your client code, all message processing on that destination will stop and depending on your configuration you may eventually fill the message store and halt processing on ALL destinations. There's a reason retries are limited to a finite number by default; what makes you sure you want an infinite number? This feels like an XY problem ( http://meta.stackexchange.com/questions/66377/what-is-the-xy-problem ); what are you ACTUALLY trying to achieve, where infinite retries is just the mechanism you've chosen to try to reach that goal? On May 14, 2015 12:06 PM, "kronos72it" <[email protected]> wrote: > I am using AMQ and have problem with DLQ because I don't like a redelivery > policy with DLQ . > My requirements are : > 1) no loosing messages and hold the correct order > 2) minimize messages in memory and hold how many possible message in > persistent storage > 3) redelivery policy : each message must be send for infinite trying number > ,then no messages in DLQ > > Despite my configuration > <http://activemq.2283324.n4.nabble.com/file/n4696500/activemq.xml> > ,during > the sending of messages from client, I see a DLQ that is populated with > some > messages, why ? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/DLQ-tp4696500.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
