Forgot to mention that consumer C uses the same client-id when connecting
to broker B and A.
On Mon, Jun 2, 2014 at 3:43 PM, Paddy Carman wrote:
> Seeking the experts help here.
>
> I have 2 brokers - A and B - connected as networks of brokers
> configuration using network connectors.
>
> P ---
Seeking the experts help here.
I have 2 brokers - A and B - connected as networks of brokers configuration
using network connectors.
P A -B-C
There is one publisher P connected to A that published to topic
/topic/foo/bar. I also have a durable subscriber C for the to
Hi all,
We have several client-brokers connected to a central broker. When restarting
client-brokers (for whatever reason), it often happens that we get
"InvalidClientIDException:... already connected from..." and
"IllegalStateException: Cannot lookup a producer from a connection that had not
Hello,
We were able to reproduce this issue with just ActiveMQ (minus our
application). It seems that when the consumers throw a exceptions
frequently, something goes wrong trying to rollback the transaction and the
LevelDB. It seems that a LevelDB thread is locking it up.
Attached is a test whic
Karaf v3.0.1
AMQ v5.9.1
feature:install activemq-broker-noweb
feature:install activemq-client
http:list
shows TWO servlets pointing to /cxf one is the standard one and is active,
the other is create by AMQ which fails to start.
has anyone seen this? if so, is there a workaround? I've had to d
some Destination interface methods, e.g. messageConsumed, are coupled in
org.apache.activemq.broker.region.BaseDestination to AdvisoryMessages flags,
e.g. advisoryForConsumed.
This way, other plugins like LoggingBrokerPlugin are not called
is there a special reason for this coupling?
actually, w
