Build Forge build service appears to stop working
Spencer Murata (2.3k●11●59●71)
| asked May 24 '12, 3:36 p.m.
FORUM MODERATOR / JAZZ DEVELOPER edited Jun 04 '12, 9:33 a.m.
Running the test connection gets a java.net.sockettimeoutexception with test connection. Also all of the Build Forge build activities appear to stop working, builds are no longer picked up, build activities are no longer updated, etc. What is causing this?
|
Accepted answer
|
There is a defect in the Build Forge API that can cause the network socket to get stuck. The defect is:
https://jazz.net/jazz08/web/projects/Rational%20Build%20Forge#action=com.ibm.team.workitem.viewWorkItem&id=25401 The root problem is that the socket timeout is not honored, which can cause the Build Forge API connection to get stuck which then keeps the RTC Build Forge services from running. This problem appears to be particular prevalent in high latency environments. The only workarounds at this time are to close the sockets manually or cycle the RTC server. Running the test connection gets a java.net.sockettimeoutexception with test connection. Also all of the Build Forge build activities appear to stop working, builds are no longer picked up, build activities are no longer updated, etc. What is causing this? Spencer Murata selected this answer as the correct answer
|
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.