I wish I knew... It usually takes hours of traffic to reproduce, but I've
also seen it sometimes happening just after starting...
Are there any relevant logs that could help in diagnosing the problem?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Producer-connections-k
Hi,
We've been experiencing some trouble with producer connections being broken
and not recovering appropriately. Or that's what we've gathered...
We're using a PooledConnectionFactory with 100 max connections, where there
are 15 producers. The rest of the parameters are kept the default in the
f
Using "masterslave:" works, although the log still shows a somewhat weird
behaviour, I've pasted it below.
It looks like broker B doesn't realize of the connection failure and rejects
at first the new incoming network connector from broker A.
(I'm not testing a failover, but a lost connection betw
That explains why I don't see the "Network connection ... has been
established" log!
And of course there's no BrokerInfo command when failover is in control,
even when only reconnecting to the master.
Excellent entry indeed!
I see it's in https://activemq.apache.org/ now too.
I'll try the masters
Did you find a solution?
I've just run into the problem too, this what I get:
2013-05-23 17:47:04,927 | DEBUG | suppressing duplicate message send
[ID:corerec2-53231-1368512827283-0:385:1:1:1] with producerSequenceId [1]
less than last stored: 9 | org.apache.activemq.broker.ProducerBrokerExchange
