RTC hangs at 97% complete when accepting change sets
Jeff Care (1.0k●38●33)
| asked Mar 06 '13, 5:12 p.m.
retagged Mar 12 '13, 1:28 p.m. by Hadar Hawk (188●22●14)
My team is experiencing a problem were occasionally the progress monitor will hang at 97% when accepting change sets. I've let it run overnight and in the morning the progress monitor is still pegged at 97%.
We're pretty clueless as to why this happens. Generally it's occurred more often when there were a large number of change sets to accept, but I've also seen it happen with only a handful. When this happens this only way to recover is to forcibly kill Eclipse & restart. More often than not the local sandbox is also either trashed or so out of sync with the server workspace that it's often less trouble to simply start over with a new local sandbox. Our server version is 3.0.1.3, build ID RJF-I20120322-1607 in case that is important. |
2 answers
Just to circle back on this problem, it was eventually determined to be a problem in WTP.
|
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.
Comments
Anything coming up in the RTC log files at all?
Also - can you turn on the metronome on the Eclipse side and see if that gives you a clue as to where things are going wrong. Of course, you need to have this one before you get the error :-)
anthony
Our server is hosted by a different team, so I don't have direct access to the logs. I may be able to get them - what log files, specifically, should I ask for?
I've turned on metronome but it's not clear how it can help me. Can you elaborate?
https://jazz.net/help-dev/clm/topic/com.ibm.team.concert.doc/topics/t_metronome.html
Once you have metronome enabled, it will record traffic with the server. You can run your accept and it will collect what calls were made and how long it spent doing certain things.
@carej Are you still seeing issues?