Re: Non-persistent jms message get lost for non durable subscriber.

2017-02-08 Thread Tim Bain
Also make sure you haven't set an unreasonably short time for JMSExpiration. On Feb 7, 2017 11:38 AM, "Timothy Bish" wrote: > Check the configuration of the Constant Pending Message Limit Strategy: > http://activemq.apache.org/slow-consumer-handling.html > > this could be tripping you up. > > On

Re: Non-persistent jms message get lost for non durable subscriber.

2017-02-07 Thread Timothy Bish
Check the configuration of the Constant Pending Message Limit Strategy: http://activemq.apache.org/slow-consumer-handling.html this could be tripping you up. On 02/07/2017 01:06 PM, Clebert Suconic wrote: Since you are looking on other possibilities, take a look on http://activemq.apache.org/ar

Re: Non-persistent jms message get lost for non durable subscriber.

2017-02-07 Thread Clebert Suconic
Since you are looking on other possibilities, take a look on http://activemq.apache.org/artemis/ as well? Anyways, a non persistence message should be available to be received as long as you didn't stop the broker. The non persistent message means the message doesn't need to survive an eventual