Hi Team,
Today observed an unusual issue related to the execution of the Data services job.
This scheduled job is scheduled daily at 05:00 in morning and sometimes it triggers appropriately at desired time
and sometimes it doesn't even get triggered.
This is abnormal behavior of the Job execution. I checked the Windows scheduler and everything is fine.
But, when checked the AL_RWJobLauncherLog file I found below errors:
Error Log :
--------------------------
(14.2.5.800) 03_15_2016 05:00:00 (10824): CRWJobLauncherApp::InitInstance called.
(14.2.5.800) 03_15_2016 05:00:10 (10824): Connected to CMS Server : <Server Name2> of CMS Cluste : @<Cluster Name>
(14.2.5.800) 03_15_2016 05:00:10 (10824): No DS Local Repositories Registred in CMS
(14.2.5.800) 03_15_2016 05:00:11 (10824): *** RWJL_EXIT called.
(14.2.5.800) 03_15_2016 05:00:11 (10824): *** ERROR: RWJobLauncher failed to connect to CMS. (BODI-1250220)
But when the Job executes fine we get the below entries in AL_RWJobLauncherLog file :
--------------------------
(14.2.5.800) 03_14_2016 05:00:01 (11024): CRWJobLauncherApp::InitInstance called.
(14.2.5.800) 03_14_2016 05:00:01 (11024): Connected to CMS Server : <Server Name1> of CMS Cluste : @<Cluster Name>
(14.2.5.800) 03_14_2016 05:00:02 (11024): Connected to CMS Server : <Server Name2> of CMS Cluste : @<Cluster Name>
(14.2.5.800) 03_14_2016 05:00:03 (11024): Launching Job (no wait, no status). inet address <inet:<Server Name1>:3500>, GUID
...
In which we can clearly see that in the error log it is not connecting to <Server Name1> of CMS Cluste : @<Cluster Name>.
Strange thing is sometimes this job executes as per schedule and sometimes it doesn't.
Please suggest if you have any idea about this.
Regards,
Santosh