I tried the 4.2 snapshot, and while I did not get any stuck messages, I did a number of concurrent modification exceptions. Interestingly with the number of clients I was running I did seem to get through all of the messages.
Also - 4.2 did not seem to balance the requests very well at all between clients. I created 2 separate clients on two different machines, both multi-threaded. It seems like the first client to start was the one that received nearly all of the messages. I dont ever remember having these problems with 3.x - so for fun? I rolled back to 3.2.2 and I ran my test app a number of times a. I never received a stuck message, nor the concurrent exception and the balancing looked very even. James.Strachan wrote: > > > James.Strachan wrote: >> >> I wonder if either of you could try out trunk to see if the problem is >> still there? There's been a number of patches in the acknowledgement >> code of late. (Unfortunatley the nightly snapshots haven't been >> working for a little while but we'll hopefully get them working again >> ASAP). >> > > Incidentally the nightly backups are back now if you wanna try a binary > download of 4.2-snapshot (pick one near the bottom thats dated January :) > > http://people.apache.org/repo/m2-snapshot-repository/org/apache/activemq/apache-activemq/4.2-incubator-SNAPSHOT/ > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > > -- View this message in context: http://www.nabble.com/Is-anyone-else-seeing-messages-stuck-on-a-queue--tf3027911.html#a8528222 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
