How to Fix the Mysterious Global Configuration Management Error in jts.log or ccm.log

I recently ran across an issue, one that was low priority, but nagging like a gnat on a hot summer day. I kept seeing these entries in the log files:

ERROR ervice.internal.GlobalConfigurationCacheUpdateTask - [operationId=976] com.ibm.team.jfs.app.http.HttpServiceUnavailableException: Unable to discover the GC service, which might indicate that Global Configuration Management is not set up in JTS. Please have your admin verify that your GC server is running, and that it is registered with JTS.

[ccm: AsynchronousTaskRunner-1 @@ 14:53] ERROR am.gc.sdk.service.internal.NotificationTimeoutTask - [operationId=144] The task to query for timed-out pending notifications failed:
Unable to discover the GC service, which might indicate that Global Configuration Management is not set up in JTS. Please have your admin verify that your GC server is running, and that it is registered with JTS.

If you are running Rational Team Concert, Quality Manager, Design Manager, or DOORs Next Generation, you may see the following errors filling up your log. If you are not running Global Configuration Management (hint: if you are the admin of the environment and don’t know if you are running GC, then you aren’t: it requires additional setup to get it working and has a particular purpose), then these are harmless errors that can be ignored. However to make it easier to search and view the ccm.log, qm.log, dm.log, or jts.log files without sifting through all these pointless errors, you can disable a setting in the admin panel for each application you are running.

To do that, go to <hostname:port>/<app>/admin#action=com.ibm.team.repository.admin.configureAdvanced . This is the advanced properties. Of course substitute hostname and port with your own environment. Substitute the <app> for each app you are running (i.e. ccm, jts, qm, rm, dm). You need to do this for each app. Search for the property “Global configuration caching”, and set these to false. Be sure to save the configuration. This should stop it from logging into your log files.

Reference: https://jazz.net/forum/questions/219800/crjaz1992e-the-comibmteamgcsdkserviceglobalconfigurationsdkglobalconfigurationcacheupdatetask-task-could-not-be-completed-and-is-now-unscheduled-in-diagnostics