Also I get: WARN | java.lang.NullPointerException
I think all the issue seems to happen when the producer is producing faster than the consumer can consume. Initially the consumer keeps up, but when I kill and restart the consumer, it slows down, likely since it is consuming from the persistent files, and that is slower. For my application, I am fine with losing older messages, which is why I have the "drop head" policy. Having the broker become unreliable is a big issue, however. -- View this message in context: http://activemq.2283324.n4.nabble.com/Reliability-issues-with-Apollo-tp4695980p4695983.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
