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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 1.3.0
• Component/s: ActiveMQ

Environment

.NET 3.5

• Patch Info: Patch Available
• Regression: Regression
• Assignee: Timothy A. Bish
• Reporter: Ted Carroll
• Created: 08/Mar/10 18:09
• Updated: 21/Feb/17 13:57
• Resolved: 10/Mar/10 15:36

Description

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.

Diagnosis:

In FailoverTransport.DoConnect() there is the following if statement:

if(ConnectedTransport != null || disposed || connectionFailure != null)

{ return false; }

else

it apears that connectionFailure is set and never reset. Then the FailoverTask.Iterate() calls into DoConnect only to return false immediately every time.

I have attached a patch, but I would be uncomfortable calling it a long term solution as I've not had the time to fully understand the code in question. However, it seems to improve the behavior.

Issue Links

• is cloned by: AMQNET-561 CLONE - NMS Failover causes CPU utilization to spike if ActiveMQ is stopped.