Re: Re: Unexpected DLQ behaviour with non-persistent messages

2020-02-05 Thread Martin Lichtin
Hi JB Yes I've enabled DLQ to accept non-persistent messages. Noone likes to loose a message for no apparent reason, i.e. simply because a consumer cannot currently handle it :-) Not persisting a message does not mean to not care about it. I've created AMQ-7397, glad to see we can make this be

Re: Unexpected DLQ behaviour with non-persistent messages

2020-02-03 Thread Jean-Baptiste Onofré
Hi Martin, Just to be sure: did you enable DLQ for non persistent message ? I'm splitted about that: as a message in DLQ never expired, I would expect that it would stay forever (as DLQ requires a "manual" action). However, I see your point: as the original message is non-persistent, what would i

Re: Re: Unexpected DLQ behaviour with non-persistent messages

2020-02-03 Thread Martin Lichtin
Hi JB, I have to disagree with this view. The JMS delivery mode should be honoured by ActiveMQ, it should not 'improve' or change the delivery mode in any way. There's no reason such a message should survive a broker re-start, in fact I'm pretty sure most everyone will expect to loose such a m

Re: Unexpected DLQ behaviour with non-persistent messages

2020-01-30 Thread Jean-Baptiste Onofré
Hi, If you enable DLQ to non-persistent message (it's disabled by default), then, IMHO, any message stored in DLQ should survive to broker restart (else it's not really a DLQ). Again, as non-persistent messages are not supposed to go in DLQ. To send the non-persistent messages to DLQ, you have to