AnsweredAssumed Answered

APM 10.1 - java agent - failbackRetryIntervalInSeconds - has the behavior changed ?

Question asked by dave.richards on Dec 14, 2015
Latest reply on Dec 15, 2015 by dave.richards

Hi

 

I am looking at the 10.1 agents in POC. We define 2 collectors in the agent profile and do not use MOM load balancing.

 

I shut down the primary collector and the agent failed over to its secondary OK, but when I started the primary collector up again, the java agent at 10.1 did not fail back.

They stayed connected to the secondary collector defined in the profile. Is this behaviour expected ?

The 9.5 agents in this cluster have actually failed back, but the 10.1 agents have not.

 

I have this set in the profile......

introscope.agent.enterprisemanager.failbackRetryIntervalInSeconds=120

 

 

We get this in the agent log......

 

12/14/15 10:04:31 AM GMT [WARN] [IntroscopeAgent.ConnectionThread] Failed to re-connect to the Introscope Enterprise Manager at sxep.wload.barclays.co.uk:25318,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (1).

12/14/15 10:04:31 AM GMT [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected controllable Agent to the Introscope Enterprise Manager at zeqc.wload.barclays.co.uk:25318,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "gbrdsr000000577", Process = "WebSphere", Agent Name = "SIT/gbrdsr000000577_wasadmin1-bmbmobilegatewayR6-server01", Active = "true".

12/14/15 10:04:31 AM GMT [INFO] [IntroscopeAgent.ConnectionThread] New list {}@0 downloaded from zeqc.wload.barclays.co.uk:25318,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory

12/14/15 10:04:31 AM GMT [INFO] [IntroscopeAgent.Agent] New list accepted

12/14/15 10:04:31 AM GMT [INFO] [IntroscopeAgent.ConnectionThread] Connected to zeqc.wload.barclays.co.uk:25318,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory in allowed mode.

Outcomes