I found a regression with offline durable subs and the JDBC store. If
there are no messages in the store the the broker is restarted, the
durable sub is ignored so subsequent messages do not get persisted.
I committed a test and fix to trunk (r1039108) that resolves the problem.
> Was this related to the client or server side? While testing ActiveMQ 5.4.1
> I discovered message loss when the master broker fails over to slave.
> This was using NMS though and I think I narrowed it down to an issue with
> the latest version of NMS.
> The issue seems very similar so am wondering now if it was actually ActiveMQ
> v5.4.1 causing the issue.
> View this message in context: http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-4-2-tp3058930p3060525.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.