Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

How can I set the value of agent connection timeout

I always meet this error, I have tried many times to set all various timeout, but it doesn't work.
Where I can set the value of agent connection timeout???


4750 3/31/11 8:44 PM EXEC -------------------------------------------------------
4751 3/31/11 8:44 PM EXEC T E S T S
4752 3/31/11 8:44 PM EXEC -------------------------------------------------------
4753 3/31/11 8:49 PM ERROR Connection to agent timed out.

0 votes



8 answers

Permanent link
I always meet this error, I have tried many times to set all various timeout, but it doesn't work.
Where I can set the value of agent connection timeout???


4750 3/31/11 8:44 PM EXEC -------------------------------------------------------
4751 3/31/11 8:44 PM EXEC T E S T S
4752 3/31/11 8:44 PM EXEC -------------------------------------------------------
4753 3/31/11 8:49 PM ERROR Connection to agent timed out.


the agent connect timeout is defined in your system configuration (Administration/System).

However, you seem to have a relatively old version of BF. The defect where the engine would declare agent connect timeout when there was no step output from the agent was fixed quite some time ago. I suggest upgrading your console and your agent, as I believe this was a fix on both sides of the protocol.

0 votes


Permanent link
I am using BF 7.1.2 and an agent with version 7.1.1.3 and I get the same type of error.

I am trying to override the step's timeout value (5 mins) by setting _TIMEOUT to 600 (apparently this value is in seconds although the documentation does not state it either way).

367 3/31/11 11:02 AM ERROR Connection to agent timed out.

Interestingly enough this timeout error occured at 5 minutes. With _TIMEOUT set to 10 seconds I get what I expect...

367 3/31/11 10:55 AM TMO Timeout after 10 seconds.


Without _TIMEOUT set at all I also get what I expect...

356 3/18/11 9:29 AM TMO Timeout after 300 seconds.


--Jeff

0 votes


Permanent link
you're seeing 2 different timeouts. One is the step timeout (the TMO timeout), and the other is the agent connection timeout I referred to earlier. There was a defect on the agent where the heartbeats were not being appropriately sent, and another on the console where they were not being processed in some conditions. As such, a "quiet" step (one with no output) would fail at the "Agent Connect Timeout" seconds, unless the step timeout was reached first.

Try a later agent version, adjust your "Agent Connect Timeout" in your system settings, or open a PMR to get support to help you through this.

0 votes


Permanent link
Could you supply the right version of BF and Agent to me? I have no idea about which version I should download.
Also could you supply the download link????
Many thanks!

0 votes


Permanent link
Could you supply the right version of BF and Agent to me? I have no idea about which version I should download.
Also could you supply the download link????
Many thanks!

The latest version of Build Forge is 7.1.2.1 and can be downloaded from the jazz.net site.

https://jazz.net/downloads/rational-build-forge/releases/7.1.2.1?p=allDownloads

0 votes


Permanent link
Could you supply the right version of BF and Agent to me? I have no idea about which version I should download.
Also could you supply the download link????
Many thanks!

The latest version of Build Forge is 7.1.2.1 and can be downloaded from the jazz.net site.

https://jazz.net/downloads/rational-build-forge/releases/7.1.2.1?p=allDownloads

If I can upgrade BF via IBM Installation Manager, it will be more convenient. :)

0 votes


Permanent link

I am having same issue. Where buildforge test connection to one of the server is intermittently failing due to TimeoutException. Telnet to buildforge agent (server port) from server is passing. Buildforge server version is 7.1.2.1 and agent version is 7.1.1.3.

Upgrading either server or agent is not in the scope. Reason we have 100 or so remote server and this is happening in only couple. How to resolve this issue. Is there any configuration parameter in the agent, which can take care of it. ? Here is test connection log

200 HELLO - BuildForge Agent v7.1.1.3-0-0034320 AUTH AuthOk["mitara"]320 SET EnvSet["BF_AGENT_VERSION","7.1.1.3-0-0034"]320 SET EnvSet["BF_AGENT_PLATFORM","linux 2.6.18-274.17.1.el5 #1 SMP Wed Jan 4 22:45:44 EST 2012"]320 EXEC Locale["C"]320 PTY Pty[*PtyPipe]320 EXEC Locale["C"]320 EXEC ExecShellPath["/bin/ksh"]300 HEARTBEAT 1310 * /usr/local/bin:/usr/bin:/bin:/usr/kerberos/bin:/vzhome/mishrra/jazz/scmtools/eclipse:/usr/local/ant/apache-ant-1.8.2/bin310 PLAT linux 2.6.18-274.17.1.el5 #1 SMP Wed Jan 4 22:45:44 EST 2012320 PING PingOk251 RESULT 0260 EORjava.util.concurrent.TimeoutExceptionat com.ibm.jas.agent.AgentConnection.checkTimeout(AgentConnection.java:64)at com.ibm.jas.agent.AgentConnection.readLine(AgentConnection.java:159)at com.ibm.jas.agent.AgentConnection.readMessage(AgentConnection.java:127)at com.ibm.jas.agent.AgentConnection.readMessage(AgentConnection.java:120)at com.ibm.jas.agent.action.ReadAgentConnection.action(ReadAgentConnection.java:41)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.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)

0 votes


Permanent link
The stack trace under the log indicates the timeout occured under the Build Forge services layer, which has a hard coded timeout value of 30 seconds.

If you encounter this type of error, you will want to verify any potential network issue that may cause a delayed response over 30 seconds.

Otherwise, you may want update the Build Forge console settings  "Server Test Frequency" and "Max simultaneous server tests" .
Where you can increase the frequency on how often the Build Forge console will perform the server test function and reduce the number of servers tested at one time.

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Mar 31 '11, 9:11 a.m.

Question was seen: 10,079 times

Last updated: Jun 27 '13, 6:50 p.m.

Confirmation Cancel Confirm