Thanks. I figured out the problem had nothing to do with ACTIVEMQ. The onMessage method was calling a DB function which was blocking.
T Márcio Geovani Jasinski wrote: > > Hi Tom, > > This is pretty strange behavior - looks like your consumer is not running > after a while. > I think you should separate the code (pub/sub) and then start a second > consumer when first is no longer taking messages from the queue. > In case second consumer stops after another 5 messages - you know the > problem resides on you consumer code. > > Check whether your consumer has message or some timeout limitation. > > -- > Márcio Geovani Jasinski > Blumenau, Santa Catarina > > -- View this message in context: http://old.nabble.com/MessageConsumer-stops-receiving-messages-tp27830923p27837601.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
