Dom <thephe...@gmail.com> writes: > Hi, > > I've starting having unusual problems with my ActiveMQ consumers, we send > object messages via JMS 24 hours a day, peaking at around 10k per second to > various different consumers. All these consumers are consuming from the same > topic, however from different physical servers. The consumers are all based > on the same abstract class (from a shared JAR). > > On our servers running Java 6 build 20 we haven't seen an issue. We have > some newer servers running in Java 6 build 26, and these servers some times > have the issue. > > The problem is; Some of the consumers will randomly simply stop consuming - > still be sent messages from ActiveMQ, just stop passing them into our code > base. After a while this causes all consumers on that topic to stop > receiving messages (once our buffer on ActiveMQ fills up).
Are you using durable subscribers? Have you seen redeliveries around the time it stops? I'm having a similar issue where a consumer just stops receiving messages from a durable topic, usually after a period of peak traffic and after a redelivery. After a while this causes the complete topic to "block". Consumers are subscribed to multiple topics and only one topic is dead, the rest continue to work normally until a consumer is restarted. Out of desperation I've upgraded the broker to a 5.6 snapshot, and now I see this issue a lot less, but still see it once a week on average. Haven't been able to tie it to java version, was happening with build 20 and now with 23. Consumers are not java at all, they are in perl and use STOMP to communicate. [...] -- Ti si arogantan, prepotentan i peglaš vlastitu frustraciju. -- Ivan Tišljar, hr.comp.os.linux
