Thanks Tim,
In most cases, the problem occurs on reboot and it can take 2 minutes for it
to come back.
Your thoughts are similar to mine, but I thought the options on the
networkConnector would have helped with that.
I tried enabled debug logging in a quiet system to see what I could find on
a r
To unsubscribe, email users-unsubscr...@activemq.apache.org, not the list
itself.
On Jun 26, 2016 7:44 AM, "vas u" wrote:
Unsubscribe
On Jun 24, 2016 10:16 AM, "FrankS" wrote:
> Hello,
>
> I am working on a project that uses a network of ActiveMQ brokers. We use
> a
> fixed set of network conn
Unsubscribe
On Jun 24, 2016 10:16 AM, "FrankS" wrote:
> Hello,
>
> I am working on a project that uses a network of ActiveMQ brokers. We use
> a
> fixed set of network connectors. The test team has been performing outage
> tests by shutting down services, killing services, and rebooting servers
What was the delay between stopping and restarting the broker? Longer than
the 3-second inactivity check?
The inability to tell that a TCP connection has been severed until a
timeout has elapsed may be contributing to this problem, and may explain
the behavior is different when you shut them down
I forgot to mention, we are using (and are currently limited to) version
5.10.2
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Zero-consumers-on-some-brokers-after-reboot-tp4713319p4713328.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
