Hey, just curious what the strategy for the next release is. I can't use
5.5.0 in production because this ConcurrentModificationException bug (full
stack trace below) is causing message loss.
Will there be a 5.5.1 very soon, pretty please?! When 5.5.0 comes out and
there is a known issue that ca
@Gary, you bet: https://issues.apache.org/jira/browse/AMQ-3276
-
Dan Checkoway
dcheckoway gmail com
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ConcurrentModificationException-in-embedded-5-5-0-broker-tp3435952p3436324.html
Sent from the ActiveMQ - User mailing lis
I think there is a problem with the way the context is referenced in
amq when threads are created, it should do nothing in that case
really. investigating now.
Can you create a jira issue to track this?
On 8 April 2011 12:32, dcheckoway wrote:
> Hello,
>
> We just migrated from ActiveMQ 5.4.2 to
We're having the same issue with SLF4J 1.5.11 (the version distributed with
ActiveMQ 5.5.0).
On Apr 8, 2011, at 7:35 AM, dcheckoway wrote:
> I suppose I should also mention that we're using slf4j 1.6.1. Not sure if
> that has anything to do with this, since the stack trace does show it
> happ
I suppose I should also mention that we're using slf4j 1.6.1. Not sure if
that has anything to do with this, since the stack trace does show it
happening in slf4j land...
org.slf4j
slf4j-api
1.6.1
runtime
org.slf4j
slf4j-jdk14
1.6.1
r
Hello,
We just migrated from ActiveMQ 5.4.2 to ActiveMQ 5.5.0. So far so good,
with one exception (pun not intended). In one case where we have an
embedded broker, we're seeing this exception get logged on occasion:
WARNING; 08-Apr-2011 11:11:41; tid:45931; TransportConnection stopAsync;
cannot
