>From my perspective, 3.2.2 was solid. I never really had any issues with it.
Here is the stack trace from the starting of activemq. Hope it helps. [EMAIL PROTECTED] bin]# ./activemq ACTIVEMQ_HOME: /usr/local/activemq-4.2 ACTIVEMQ_BASE: /usr/local/activemq-4.2 Loading message broker from: xbean:activemq.xml INFO BrokerService - Using Persistence Adapter: JournalPersistenceAdapator(JDBCPersistenceAdaptor([EMAIL PROTECTED])) INFO BrokerService - ActiveMQ null JMS Message Broker (localhost) is starting INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/ INFO ManagementContext - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi INFO JDBCPersistenceAdapter - Database driver recognized: [apache_derby_embedded_jdbc_driver] INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock to become the Master broker INFO DefaultDatabaseLocker - Becoming the master on dataSource: [EMAIL PROTECTED] INFO JournalPersistenceAdapter - Journal Recovery Started from: Active Journal: using 5 x 20.0 Megs at: /usr/local/activemq-4.2.0-snapshot/apache-activemq-4.2-incubator-SNAPSHOT/activemq-data/journal INFO JournalPersistenceAdapter - Journal Recovered: 1 message(s) in transactions recovered. INFO TransportServerThreadSupport - Listening for connections at: tcp://mdl1.myco.com:61616 INFO TransportConnector - Connector openwire Started INFO TransportServerThreadSupport - Listening for connections at: ssl://mdl1.myco.com:61617 INFO TransportConnector - Connector ssl Started INFO TransportServerThreadSupport - Listening for connections at: stomp://mdl1.myco.com:61613 INFO TransportConnector - Connector stomp Started INFO NetworkConnector - Network Connector default-nc Started INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:mdl1.myco.com-56746-1169487078117-1:0) started INFO TransportConnector - Connector vm://localhost Started INFO KahaStore - Kaha Store successfully deleted data directory activemq-data/localhost/tmp_storage ERROR Service - Async error occurred: java.util.ConcurrentModificationException java.util.ConcurrentModificationException at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:761) at java.util.LinkedList$ListItr.next(LinkedList.java:696) at org.apache.activemq.broker.region.cursors.VMPendingMessageCursor.next(VMPendingMessageCursor.java:71) at org.apache.activemq.broker.region.PrefetchSubscription.dispatchMatched(PrefetchSubscription.java:380) at org.apache.activemq.broker.region.PrefetchSubscription.pullTimeout(PrefetchSubscription.java:111) at org.apache.activemq.broker.region.PrefetchSubscription.access$000(PrefetchSubscription.java:49) at org.apache.activemq.broker.region.PrefetchSubscription$1.run(PrefetchSubscription.java:94) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) ERROR Service - Async error occurred: java.util.ConcurrentModificationException java.util.ConcurrentModificationException at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:761) at java.util.LinkedList$ListItr.next(LinkedList.java:696) at org.apache.activemq.broker.region.cursors.VMPendingMessageCursor.next(VMPendingMessageCursor.java:71) at org.apache.activemq.broker.region.PrefetchSubscription.dispatchMatched(PrefetchSubscription.java:380) at org.apache.activemq.broker.region.PrefetchSubscription.pullTimeout(PrefetchSubscription.java:111) at org.apache.activemq.broker.region.PrefetchSubscription.access$000(PrefetchSubscription.java:49) at org.apache.activemq.broker.region.PrefetchSubscription$1.run(PrefetchSubscription.java:94) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) ERROR Service - Async error occurred: java.util.ConcurrentModificationException <This then repeats another 1/2 dozen times or so > Thanks rajdavies wrote: > > wow! 3.2.2 was solid! Could you post the stack trace with the > concurrent modification exceptions please ? > > cheers, > > Rob > > On 23 Jan 2007, at 19:10, YoungSoul wrote: > >> >> >> 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. >> > > > -- View this message in context: http://www.nabble.com/Is-anyone-else-seeing-messages-stuck-on-a-queue--tf3027911.html#a8550623 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
