""CRJAZ1992E The com.ibm.team.gc.sdk.service.GlobalConfigurationSdk.GlobalConfigurationCacheUpdateTask task could not be completed and is now unscheduled" in diagnostics
Running CLM 6.0.1 with ifix03.
JTS Diagnostics error...."CRJAZ1992E The "com.ibm.team.gc.sdk.service.GlobalConfigurationSdk.GlobalConfigurationCacheUpdateTask" task could not be completed and is now unscheduled. Error details: "Software caused connection abort: recv failed"
I searched through JTS and CCM logs and couldn't find any reference to CRJAZ1992E error.
Restarting the server seems to clear the error, but it eventually comes back. Any ideas?
JTS Diagnostics error...."CRJAZ1992E The "com.ibm.team.gc.sdk.service.GlobalConfigurationSdk.GlobalConfigurationCacheUpdateTask" task could not be completed and is now unscheduled. Error details: "Software caused connection abort: recv failed"
I searched through JTS and CCM logs and couldn't find any reference to CRJAZ1992E error.
Restarting the server seems to clear the error, but it eventually comes back. Any ideas?
Accepted answer
Hi, Matthew
It is not clear that if you have Global Configuration*gc) application installed and if you are intending to use GC features or not. You may not see the same error code in jts.log file but jts.log may still reveal something at the timeframe when you ran jts diagnostics. you can also set log4j.logger.com.ibm.team.gc.sdk.service=DEBUG to jts log4j.properties file
(need to reload setting if you know how to do that to make the setting effective or restart server) and re-run jts diagnose and then check with the log files and see if it may reveal more info.
If you are not intending to use gc, in gc admin page there are properties handling the GlobalConfigurationCacheUpdateTask. Setting the time to -1 might disable it.
<serverurl>/gc/admin#action=com.ibm.team.repository.admin.configureAdvanced
(https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.jazz.vvc.doc/topics/c_cm_cfg-settings.html&scope=null)
The setting has a time make it -1, It fails once, and then never runs again. So, it's a one-time problem.
It is not clear that if you have Global Configuration*gc) application installed and if you are intending to use GC features or not. You may not see the same error code in jts.log file but jts.log may still reveal something at the timeframe when you ran jts diagnostics. you can also set log4j.logger.com.ibm.team.gc.sdk.service=DEBUG to jts log4j.properties file
(need to reload setting if you know how to do that to make the setting effective or restart server) and re-run jts diagnose and then check with the log files and see if it may reveal more info.
If you are not intending to use gc, in gc admin page there are properties handling the GlobalConfigurationCacheUpdateTask. Setting the time to -1 might disable it.
<serverurl>/gc/admin#action=com.ibm.team.repository.admin.configureAdvanced
(https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.jazz.vvc.doc/topics/c_cm_cfg-settings.html&scope=null)
The setting has a time make it -1, It fails once, and then never runs again. So, it's a one-time problem.
Comments
