Hello everyone, We have a network of 5 brokers communicating via TCP on the default connector. We are running around 300,000 messages per hour on each broker through a series of queues. On every broker there is a point in time where it hits a ConcurrentModificationException (see https://issues.apache.org/activemq/browse/AMQ-1971) and they no longer dispatch messages afterwards thereby freezing all of the queues.
This seems like a critical bug in a release candidate (or soon to be candidate) so I wanted to post it to the list to see if others have encountered it, or if there were ideas on a quicker fix. The code is in the midst of a few resource locks and is in a very important part of the broker, so I am nervous about attempting a patch without knowing more about how the inner workings behave Any thoughts on the problem? -- Jayson -- View this message in context: http://www.nabble.com/Threading-problem-in-ActiveMQ-5.2.0-%28from-SVN-tag%29-causing-ConcurrentModificationException-tp19937218p19937218.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
