[AMQNET-561] CLONE - NMS Failover causes CPU utilization to spike if ActiveMQ is stopped.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.7.2
• Component/s: ActiveMQ

Environment

.NET 3.5

• Patch Info: Patch Available
• Regression: Regression
• Assignee: Timothy A. Bish
• Reporter: Oleg Kozakevych
• Created: 21/Feb/17 13:57
• Updated: 21/Feb/17 14:16

Description

Looks like the issue reappeared again.

1) Configure a simple program that attempts to connect to ActiveMQ with the url "activemq:failover:(tcp://localhost:61616)"
2) Make sure activemq is not running on the local host
3) Try to connect.
4) Notice that the CPU utilization in the sample program is high.
5) Start ActiveMQ.
6) Notice that the connection is successful but the CPU utilization remains high.

Expected:
I expect, potentially, an initial spike in CPU utilization but not sustained high CPU.

The stack points to the TcpTransport.ReadLoop() method.
I tried to add Thread.Sleep(10); into this loop and CPU isn't consumed, but I suppose this is not a good fix for that problem.

Issue Links

• is a clone of: AMQNET-241 NMS Failover causes CPU utilization to spike if ActiveMQ is stopped.