It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787

question asked: May 09 '12, 4:45 p.m.
question was seen: 6,144 times
last updated: Dec 05 '12, 12:58 p.m.

Related questions

FAQ - How this Forum works

Build Agent TMO Timeout after +300 seconds.

0
Michael Gray (86●12●6) | asked May 09 '12, 4:45 p.m.
edited Dec 05 '12, 12:58 p.m.
I'm trying to make use of Rational Build Agent - Command Line builds as
an alternative to having to manage an ever-increasing number of JBE
processes on our build farm systems.

I've got a simple test build set up which connects, executes pre-build,
build, and post-build commands -- now I'm trying to add the Jazz Source
Control component. Things seem to go along fine for a while, but after
300 seconds of fetching (I'm testing with a big file tree), I get a timeout.
Anyone know where/how to increase this 300 second timer?

SCRIPT E:\jazz\3.0.1\buildsystem\buildengine\eclipse\jbe -vm E:\jazz\3.0.1\client\eclipse\jdk\bin\java -userId ***** -passwordFile ***** -repository https://*****/jazz/ -buildResultUUID _iDcCIJnxEeGGkqDTJhes-A -engineUUID _IpZBAJk-EeGbeYW34Z4BAQ -participants com.ibm.team.build.jazzscm -noComplete -verbose
EXEC start "\"@"*****"
* Supplied arguments:
* -userId ***** -passwordFile ***** -repository https://*****/jazz/ -buildResultUUID _iDcCIJnxEeGGkqDTJhes-A -engineUUID _IpZBAJk-EeGbeYW34Z4BAQ -participants com.ibm.team.build.jazzscm -noComplete -verbose
* Java Version:
* J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223ifx-20100511 (JIT enabled)
* J9VM - 20100509_57823_lHdSMr
* JIT - 20091016_1845ifx7_r8
* GC - 20091026_AA
* 2012-05-09 12:11:04 Searching for buildResultUUID=_iDcCIJnxEeGGkqDTJhes-A
* 2012-05-09 12:11:04 The -noComplete parameter specified, build result will not be completed by JBE.
* 2012-05-09 12:11:04 Building only the specified participants: ""
* 2012-05-09 12:11:04 Not using a proxy to reach https://*****/jazz/
* 2012-05-09 12:12:14 Searching for build request...
* 2012-05-09 12:12:15 Found a user request for build definition "lmgray-bfagent-test".
* 2012-05-09 12:12:15 Build participant "com.ibm.team.build.cmdline" was not specified on -participants list.
* 2012-05-09 12:12:15 Build participant "com.ibm.team.build.ant" was not specified on -participants list.
* 2012-05-09 12:12:15 Build participant "com.ibm.team.build.maven" was not specified on -participants list.
* 2012-05-09 12:12:15 Build participant "com.ibm.team.build.junit.publishing" was not specified on -participants list.
* 2012-05-09 12:12:15 Build participant "com.ibm.team.build.jdt.publishing" was not specified on -participants list.
* 2012-05-09 12:12:15 Build participant "com.ibm.team.build.msbuild" was not specified on -participants list.
* 2012-05-09 12:12:15 Build participant "com.ibm.team.build.mstest.config" was not specified on -participants list.
* 2012-05-09 12:12:15 Build participant "com.ibm.team.build.nunit.config" was not specified on -participants list.
* 2012-05-09 12:12:15 Build participant "com.ibm.team.build.autoDeliver" was not specified on -participants list.
* 2012-05-09 12:12:15 Should build occur?
* 2012-05-09 12:12:15 Yes: Always build a user initiated request.
* 2012-05-09 12:12:15 CRRTC3507W: Warning: No engine participant found for pre_build configuration element "Pre-Build Command Line".
* 2012-05-09 12:12:15 Invoking pre-build participant "com.ibm.team.build.jazzscm"
TMO Timeout after +300 seconds.
RESULT 500
EOR
Status:ERROR

6 answers

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Michael Gray (86●12●6) | answered May 10 '12, 4:03 p.m.
I'm on Windows with bfagent running as a service and don't see startbfa.sh or equivalent bat/cmd file -- is there an equivalent startup script/mechanism for Windows where this can be set?


I found it! I was able to set a property in the build def named _TIMEOUT
and the build agent seems to respect it. My long-running fetch using
JBE_COMMAND now works.

Thanks for pointing me in the right direction!
Comments
Rafael Verceze commented Dec 05 '12, 12:54 p.m.

Hi i was having the same problem and im using BA as a windows server,where did you set this _TIMEOUT property?

Michael Gray commented Dec 05 '12, 12:58 p.m.

I set _TIMEOUT as a property in the RTC build definition.
0
permanent link
Steven Zheng (217●4●5) | answered May 10 '12, 3:16 a.m.
JAZZ DEVELOPER
Are you using JBE or Rational Build Agent now?
If Rational Build Agent, you can change the "#read_timeout 1800"
to "read_timeout xxxx" in bfagent.conf(the unit is seconds).
0
permanent link
Michael Gray (86●12●6) | answered May 10 '12, 8:20 a.m.
Are you using JBE or Rational Build Agent now?
If Rational Build Agent, you can change the "#read_timeout 1800"
to "read_timeout xxxx" in bfagent.conf(the unit is seconds).


I'm using Rational Build Agent -- I made that change and restarted the
bfagent service before posting this question. Changing read_timeout 1800
in bfagent.conf did not seem to have any effect. I still get TMO Timeout
after +300 seconds.
0
permanent link
Michael Gray (86●12●6) | answered May 10 '12, 8:53 a.m.
I've changed read_timeout to 3600 and re-tested -- still get the following
after 5 minutes of fetching:

TMO Timeout after +300 seconds.
RESULT 500
EOR
Status:ERROR
0
permanent link
Steven Zheng (217●4●5) | answered May 10 '12, 9:25 a.m.
JAZZ DEVELOPER
Try modify startbfa.sh then:


# If you want to set the timeout for the build step execution,
# uncomment the following line and specify the timeout value
# in seconds. If it is not specified, the default value 300
# seconds will be used.
#
export _TIMEOUT=3600
0
permanent link
Michael Gray (86●12●6) | answered May 10 '12, 10:18 a.m.
I'm on Windows with bfagent running as a service and don't see startbfa.sh or equivalent bat/cmd file -- is there an equivalent startup script/mechanism for Windows where this can be set?

Your answer

Register or 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.