AgentConnection.checkTimeout exceptions filling log
Running 7.1.2.2 ifix1
There are repeated exception entries in catalina.out for AgentConnection.checkTimeout related to the same Server. The Server entry shows red status as expected, but the test results show 'Connection Timeout' instead of 'Connection Refused'. It looks like the agent process is tying up the port, but it's unresponsive. Telneting to the agent results in 'Connection timed out'.
Is there a way to exclude these exceptions from catalina.out?
Sep 2, 2011 12:27:10 PM com.ibm.jas.fiber.FiberThread$1 uncaughtException
SEVERE: Exception in fiber "ServicesLayer"
java.util.concurrent.TimeoutException
at com.ibm.jas.agent.AgentConnection.checkTimeout(AgentConnection.java:64)
at com.ibm.jas.agent.AgentConnection.connect(AgentConnection.java:86)
at com.ibm.jas.agent.action.OpenAgentConnection.action(OpenAgentConnection.java:26)
at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197)
at com.ibm.jas.fiber.action.flow.Block.action(Block.java:63)
at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197)
at com.ibm.jas.agent.AgentFiber.action(AgentFiber.java:234)
at com.ibm.jas.agent.AgentFiber$AgentFiberAction.action(AgentFiber.java:339)
at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197)
at com.ibm.jas.fiber.Fiber.runFiber(Fiber.java:670)
at com.ibm.jas.fiber.FiberThread.runFibers(FiberThread.java:258)
at com.ibm.jas.fiber.FiberThread.run(FiberThread.java:246)
There are repeated exception entries in catalina.out for AgentConnection.checkTimeout related to the same Server. The Server entry shows red status as expected, but the test results show 'Connection Timeout' instead of 'Connection Refused'. It looks like the agent process is tying up the port, but it's unresponsive. Telneting to the agent results in 'Connection timed out'.
Is there a way to exclude these exceptions from catalina.out?
Sep 2, 2011 12:27:10 PM com.ibm.jas.fiber.FiberThread$1 uncaughtException
SEVERE: Exception in fiber "ServicesLayer"
java.util.concurrent.TimeoutException
at com.ibm.jas.agent.AgentConnection.checkTimeout(AgentConnection.java:64)
at com.ibm.jas.agent.AgentConnection.connect(AgentConnection.java:86)
at com.ibm.jas.agent.action.OpenAgentConnection.action(OpenAgentConnection.java:26)
at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197)
at com.ibm.jas.fiber.action.flow.Block.action(Block.java:63)
at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197)
at com.ibm.jas.agent.AgentFiber.action(AgentFiber.java:234)
at com.ibm.jas.agent.AgentFiber$AgentFiberAction.action(AgentFiber.java:339)
at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197)
at com.ibm.jas.fiber.Fiber.runFiber(Fiber.java:670)
at com.ibm.jas.fiber.FiberThread.runFibers(FiberThread.java:258)
at com.ibm.jas.fiber.FiberThread.run(FiberThread.java:246)
One answer
Running 7.1.2.2 ifix1
There are repeated exception entries in catalina.out for AgentConnection.checkTimeout related to the same Server. The Server entry shows red status as expected, but the test results show 'Connection Timeout' instead of 'Connection Refused'. It looks like the agent process is tying up the port, but it's unresponsive. Telneting to the agent results in 'Connection timed out'.
Is there a way to exclude these exceptions from catalina.out?
Sep 2, 2011 12:27:10 PM com.ibm.jas.fiber.FiberThread$1 uncaughtException
SEVERE: Exception in fiber "ServicesLayer"
java.util.concurrent.TimeoutException
at com.ibm.jas.agent.AgentConnection.checkTimeout(AgentConnection.java:64)
at com.ibm.jas.agent.AgentConnection.connect(AgentConnection.java:86)
at com.ibm.jas.agent.action.OpenAgentConnection.action(OpenAgentConnection.java:26)
at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197)
at com.ibm.jas.fiber.action.flow.Block.action(Block.java:63)
at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197)
at com.ibm.jas.agent.AgentFiber.action(AgentFiber.java:234)
at com.ibm.jas.agent.AgentFiber$AgentFiberAction.action(AgentFiber.java:339)
at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197)
at com.ibm.jas.fiber.Fiber.runFiber(Fiber.java:670)
at com.ibm.jas.fiber.FiberThread.runFibers(FiberThread.java:258)
at com.ibm.jas.fiber.FiberThread.run(FiberThread.java:246)
Hi,
You should mark the server as disabled until the agent on the host system can be checked out. On the server page in the UI there is a checkbox for 'Disable'.
Brent Ulbricht
RTC Build Lead