RTC build reports a socket timeout
When trying to run a build in JBE, the following message appears:
connection failed: CRJAZ0099I When accessing the URL "https://localhost:9443/jazz/service/com.ibm.team.filesystem.common.
IFilesystemService" the following HTTP error occurred: "java.net.
SocketTimeoutException"
How can I keep the JBE from timing out?
Accepted answer
The first thing to try is bump up the JBE time out value. Add the arguments "-vmargs -Dcom.ibm.team.repository.common.transport.
TeamServerConfiguration.socketTimeout=900000 " to the end of the JBE execution string.
TeamServerConfiguration.socketTimeout=900000 " to the end of the JBE execution string.
However this is just the JBE level time out. The timeout could also be caused at the web application and web server level. This could especially be true if the JBE build is using the SCM build participant and is trying to pull in a large file set. In those cases you will have to increase the timeouts at the Tomcat or WAS level, as they could easily be terminating the connection on the server side.
Comments
What timeouts in j2ee server ?
I'm not totally familiar with all of the settings available for Tomcat and WAS around this, but generally they are the timeouts that control session length.
~Spencer
Thanks,
session-timeout I guess. Our experience on these build timeout is that they are more impacted by repository timeout.
I assume this property can be appended to the -vmargs section of the jbe.ini too?
Yes it can.