It's all about the answers!

Ask a question

""CRJAZ1992E The task could not be completed and is now unscheduled" in diagnostics

Matthew Clark (97425) | asked Apr 11 '16, 9:27 a.m.
edited Sep 26 '16, 9:49 a.m. by Krzysztof Kaźmierczyk (7.4k34795)
Running CLM 6.0.1 with ifix03.

JTS Diagnostics error...."CRJAZ1992E The "" 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

permanent link
Don Yang (7.2k2194127) | answered Apr 11 '16, 7:22 p.m.
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 to jts 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.

The setting has a time make it -1, It fails once, and then never runs again. So, it's a one-time problem.

Matthew Clark selected this answer as the correct answer

Matthew Clark commented Apr 11 '16, 8:10 p.m.

Hello Don,

Thanks for the response. We do not have the Global Configuration application installed. With the upgrade to 6.0.1, we installed both the DCC and LQE applications. The error started around the same time as the upgrade. Since there is no GC application, can the  GlobalConfigurationCacheUpdateTask exist elsewhere?

It also mentions that it's going to be unscheduled. I remember scheduling the data collections jobs for DCC, could that have something to do with it?

Don Yang commented Apr 11 '16, 11:12 p.m. | edited Apr 12 '16, 2:10 a.m.

Hi, Matthew

I think the issue here is that Foundation includes the GC SDK, and this will always be installed, regardless of whether the GCM application it references is deployed or not. This is required at installation time because of supporting a federated deployment where GCM is installed on one machine and registered against a JTS,  but referenced from application instances on other machines that might be registered with other JTSs deployed on other machines.

The error message itself is harmless if GCM is not installed. If GCM is not installed , you can set the Advanced Property 'Global Configuration caching' to "false". The task will still be scheduled to run, but not actually do anything, so no errors should be logged. You need to do this for each registered application (e.g. jts/admin, ccmContextRoot/admin, rmContextRoot/admin, qmContextRoot/admin) where this message is being logged.

Matthew Clark commented Apr 12 '16, 4:34 p.m.

Thank you!

Your answer

Register or to post your answer.