It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,876
×7,467
×6,034
×1,193

question asked: Jan 08 '16, 8:11 a.m.
question was seen: 4,014 times
last updated: Jan 08 '16, 10:48 a.m.

Related questions

TeamAccept Socket timeout

0
N. VD (84●27●34) | asked Jan 08 '16, 8:11 a.m.
 Out builds fail with this error:

[teamAccept] com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0099E An HTTP error occurred when this URL was being accessed: /ccm/service/com.ibm.team.scm.common.IScmService. Error details: java.net.SocketTimeoutException.

The builds are headless via ANT script.

How can i increase the timeout settings for the [teamAccept] ANT task ?

http://www-01.ibm.com/support/knowledgecenter/SSCP65_2.0.0.2/com.ibm.team.build.doc/topics/r_teamaccept.html

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Jan 08 '16, 9:01 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I don't think you can change this timeout and I am not sure you want to either.
You want to find out why you have a socket timeout. Questions would be:

  • Does the fetch connect at all from the build machine?
  • Is the performance of the RTC Server affected by something?
  • Are the Eclipse clients able to load workspaces?
  • What is happening in your network or system to cause a socket to be so unresponsive?
  • Should I introduce a caching proxy that is used by the build engines, instead of always loading all data from the RTC server?
Comments
N. VD commented Jan 08 '16, 10:48 a.m.

 Is there any way to check what's taking so long? 

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.