|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
After some debugging with IBM it really seems to be a race condition (at least that's their current theory):
8<---8<--My theory of a 'possible cause' is at this time.
----------------------------------------------------------------
There can only be one view_server process per view (fact)
The 'cleartool endview -server' command kills the view server process of the view.
The message about this reaches the client BEFORE the current view server process is ACTUALLY stopped (my assumption at this time)
The next command 'catcs' should start a new view server process but because the 'old' views server process is not truly killed.,,it will try to contact the 'dying' view_server process...and we get the error message
The view_server process is running on the 'view server' which in this case is the local build machine.
8<-8<--Is it possible to make the 'cleartool endview / cleartool catcs' command concatenation more robust? Or is that cleartool endview needed at all?