Thanks for your reply James, I am not seing any exceptions coming out of onMessage.
I ran more tests and things are more complicated than I first thought. When I run 100 sends/receives, JMX shows a QueueSize=100 and DispatchCount=100 after the test has run, where I was expecting QueueSize=0 (since all messages have been received). But if I run with higher numbers, for instance 1000, than the QueueSize follows DispatchCount till about 650 and then sudenly drops to 0 and starts growing again. It pretty much looks as if the actual removal is delayed. Is this some optimization mechanism I missed? Thanks again for your help Fady James.Strachan wrote: > > On 22/01/2008, Fady <[EMAIL PROTECTED]> wrote: >> >> Hello, >> >> I am new to JMS and ActiveMQ so I am probably doing something stupid but >> can't figure out what it is: >> >> I am running ActiveMQ 5.0.0 imbedded in a Tomcat application. I have a >> non-persistent producer, from a non-transacted and autoacknowledge >> session, >> creating messages in a queue and a MessageListener processing them in an >> onMessage event. >> >> Everything goes fine apart from the queue size which keeps growing (as >> reported by JMX). > > If the queue size is growing, do you have a producer sending more > messages? > > >> I was assuming messages would be automatically removed once the onMessage >> method terminates. > > It should be. > > Does your onMessage() method definitely complete without throwing any > exceptions? > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com > > -- View this message in context: http://www.nabble.com/Messages-are-not-removed-from-queue-after-onMessage-is-fired-tp15018971s2354p15023989.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
