The inactivity monitor is supposed to keep the connection from timing out,
but clearly that's not happening. You haven't done anything to
intentionally disable its keepalive feature, have you? I don't see anything
in your config files, but I want to make sure.
Tim
On Nov 13, 2017 3:54 AM, "Shobha
I believe that no messages are being passed because you haven't enabled any
destinations to be sent across the network bridge. I see you're excluding
some, but you're not including any so the exclusion has no effect.
Tim
On Nov 13, 2017 2:59 AM, "Shobhana" wrote:
> Hi,
>
> I have a network of b
I see a bunch of these messages in the logs of Node-2 :
2017-11-13 15:30:06,506 | INFO | Establishing network connection from
vm://SecondaryBroker?create=false&async=false to tcp://x.x.x.x:61616 |
org.apache.activemq.network.DiscoveryNetworkConnector | ActiveMQ Task-4
2017-11-13 15:37:49,129 | IN
Sent: 28 March 2014 16:08
To: users@activemq.apache.org
Subject: Re: Messages stuck in broker, requires restart.
there was a contention issue around the cursor cache, that could be avoided
with - that may be what you are seeing. It
could be worth a try.
On 28 March 2014 11:04, Donnell Alwyn w
there was a contention issue around the cursor cache, that could be
avoided with - that may be what
you are seeing. It could be worth a try.
On 28 March 2014 11:04, Donnell Alwyn wrote:
> Hi
>
> I'm using activmq 5.7.0, stress testing has revealed a problem in that
> messages get stuck in the b
