Symptoms
Occasionally a BusinessObjects DataServices job with Maxruntime + Kill-process runs repeatedly into Exception while killing the job causing a flood of OperatorMessages
Cause
JCS-139002: Bobj Invalid Response: The batch job is not started
Workaround
Submit Definition System_ForceJobStatusUnknown to set job to Unknown
Affected version
RunMyJobs 9.2.x
Resolution
This issue will be fixed in a future version
Reference
RCORE-41674
Error
ERROR 2023-04-11 08:21:59,460 GMT [Redwood Process Server ... #46] com.redwood.scheduler.connector.sap.bobj.jobs.impl.DataServicesJobRun - Exception while killing job: 2157021
com.redwood.scheduler.connector.sap.bobj.exception.BobjInvalidResponseException: JCS-139002: Bobj Invalid Response: The batch job is not started.
at com.redwood.scheduler.connector.sap.bobj.dataservices.connection.impl.DataServicesConnectionImpl.callDataServices(DataServicesConnectionImpl.java:537) ~[bobj-service.jar:?]
at com.redwood.scheduler.connector.sap.bobj.dataservices.connection.impl.DataServicesConnectionImpl.stopJob(DataServicesConnectionImpl.java:265) ~[bobj-service.jar:?]
at com.redwood.scheduler.connector.sap.bobj.jobs.impl.DataServicesJobRun.kill(DataServicesJobRun.java:81) [bobj-service.jar:?]
at com.redwood.scheduler.connector.sap.bobj.service.BObjJobWorker.kill(BObjJobWorker.java:79) [bobj-service.jar:?]
at com.redwood.scheduler.connector.sap.bobj.service.BObjService.killJob(BObjService.java:791) [bobj-service.jar:?]
at com.redwood.scheduler.core.processserver.ProcessServerRuntime.killJob(ProcessServerRuntime.java:942) [core.jar:?]
at com.redwood.scheduler.core.processserver.ProcessServerRuntime.onMessage(ProcessServerRuntime.java:218) [core.jar:?]
at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(MessageEnabledWork.java:122) [infrastructure.jar:?]
at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.java:135) [infrastructure.jar:?]
at java.lang.Thread.run(Thread.java:833) [?:?]
Comments
0 comments
Please sign in to leave a comment.