By 'blocking the queue' do you just mean messages were not dispatched to consumers? If so how many messages were on the queue, how many connections & consumers did the broker think were open & what were the prefetch values? If you are having trouble of dead connections not being closed down agressively enough then your issue could just be an effect of messages being placed into prefetch buffers for clients that have not been detected as failed yet? Do you have any kind of JUnit test case that can replicate your issue?
On 7/3/06, Igor Bogicevic <[EMAIL PROTECTED]> wrote:
I am using activemq 4.0.1 (I've did tests on the both 4.0.0 and 4.0.1) and I have attached activemq.xml (basically, almost out of the box configuration). I am using persistent queues, and I have tried with prefetching and transactions, but that didn't really change the behavior. Thanks, Igor On 7/3/06, James Strachan <[EMAIL PROTECTED]> wrote: > On 6/30/06, Igor Bogicevic <[EMAIL PROTECTED]> wrote: > > I also forgot to answer on this thread... this was not the problem > > related to the lack of the memory, it's related to hanging > > connections, i've set up the broker with the large amount of memory > > (>2GB) in both broker configuration and via jconsole and problem was > > defintely in the connections which were not cleaned up - for unknown > > reason to me. it was easy to block queue with large number of > > un-properly closed sessions and relatively hard with properly closed > > connections in a shutdown hook. > > Using what version and what quality of service? e.g. are we talking > 4.0.1 and non-persistent queues? What was your XML config file? > > -- > > James > ------- > http://radio.weblogs.com/0112098/ >
-- James ------- http://radio.weblogs.com/0112098/
