It's all about the answers!

Ask a question

Avoiding connection timeout on accepting a large volume of change sets with distributed SCM

Jase Alpers (132) | asked Feb 13 '17, 9:03 p.m.

We've recently configured distributed SCM between 2 RTC servers so that we can flow code from a stream in the source RTC to a stream in the target RTC.  I can create a workspace in the target RTC and "accept" code to it from the source RTC stream at a component level for small components.

Attempting to accept code for a (much) larger component times out after about 3 hours which happens to be the maximum timeout value of 9999 seconds.  Obviously, we don't want to have to reorganize the source stream just to be able to flow change sets from the source RTC stream to the target RTC stream.  Is there any other way to get around this problem?  Can we accept a limited number of change sets in batches until we're up-to-date on the target stream?  Any way to have a larger timeout value than 9999 seconds?

Alternatively, if this is not possible could we load the code as-is in the source and start accepting change sets from this point forward (obviously that is not ideal, but better than nothing).

Thanks in advance for the help!

Accepted answer

permanent link
Ralph Schoon (63.2k33646) | answered Feb 14 '17, 2:27 a.m.

 You should consider to pick an early baseline and replicate that first. then pick a later baseline and so forth.

Jase Alpers selected this answer as the correct answer

Jase Alpers commented Feb 17 '17, 12:47 p.m.

This did the trick.  Thanks very much!

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.