Message "Job manager has been shut down." appears within output of scm.exe utility
Environment: RTC 4.0.2 (both client and server) We encountered problems with output of scm.exe command. The common pattern is that the emitted output (stdout) of scm command contains error message "java.lang.IllegalStateException: Job manager has been shut down." followed by stack trace. This occured for both raw and JSON formatted output in many cases of using scm. Commands that caused described problems:
We have encountered 3 following cases:
The crucial things:
Note: We are switching from RTC 4.0 to 4.0.2. We did not encounter the described problems ever before.
Regards,
|
5 answers
There are a few work items that appear related:
IllegalStateException: Job manager has been shut down in CLI on z/OS (239599) [cli] "java.lang.IllegalStateException: Job manager has been shut down" after scm deliver (238735) UpdateChangesJob scheduled during shutdown (217382) Could you subscribe to UpdateChangesJob scheduled during shutdown (217382) and provide the information provided here for further investigation please? Comments
Petr Lidman
commented Apr 16 '13, 7:02 a.m.
There is one key question there - or rather a problem which blocks our efforts of upgrading RTC to version 4.0.2: Can it be guaranteed that the result of the requested scm operation succeeded in case when scm command returns "success" but the output (raw or JSON) contains "Job manager has been shut down." exception incl. stack trace? If the answer is yes, we will just ignore this exception in our code - it is a problem in JSON output because exception messages such as this one fail the subsequent JSON parsing (the messages break the JSON format). But we already do that with another problem type ("Job found still running after platform shutdown..."), so we would just add this one. Another topic would be why we are getting these errors in the first place - but I lack the ambition to get that one resolved if we can work around it :-).
Thanks!
|
RTC client 4.0.2 Win7 x64
4/22/2013 2:45:08 PM: Executing: "C:\Program Files (x86)\IBM\Rational Team Concert Client for Microsoft Visual Studio IDE\3rd Party\scmtools\eclipse\scm.exe" -a n create changeset -r "https://jazz/ccm/" -d "D:\Sandbox\tstbx" -w "_WVslsczwEFG81f7V5YZT5g" --no-current -j --component "ws_bx"
|
We're seeing the same thing on RTC 4.0.6 (4.0.5 Build Toolkit). WIndows 7, 64-bit:
This is preventing our Maven implementation from moving forward.
Any ideas? |
What we did... we are now ignoring all std-err output from scm.exe command line tool. Btw we are seeing "Job manager has been shut down" error message after almost all scm.exe call in RTC client 4.0.5 :(
Comments
Jason MacDonald
commented Mar 19 '14, 3:03 p.m.
Cool, thanks -- in our case we're using the Jazz SCM provider (essentially a wrapper to scm commands), so I'm not sure how we'd ignore std-err.
|
I am also getting this in v4.0.6 on Windows 32-bit scmtools. Apparently v5.0.0 has a fix for it http://www-01.ibm.com/support/docview.wss?uid=swg1PI15553
|
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.