Symptoms
RMJ PeopleSoft jobs stuck in Running after an incident in PeopleSoft
Cause
- Killing a PeopleSoft job in RMJ will not remove the job from the RMJ monitoring component.
- When active jobs are not found in PeopleSoft anymore an error is retrieved, however this error is not handled correctly by the RMJ monitoring component.
Workaround
- stop PeopleSoft process server
- put Running RMJ PeopleSoft Jobs to status Unknown
- start PeopleSoft process server
Affected version
RunMyJobs 2023.3
Resolution
This issue is fix in 2024.1.0.0
Reference
RCORE-46716
Error
Stdoud.log
ERROR 2024-01-03 23:54:56,827 GMT [Redwood PeopleSoftMonitoringComponent Thread Pool: PSOFT_OPSHR.PS_GW_PSOFT.PeopleSoftService #4c] com.redwood.scheduler.api.model.job.peoplesoft.err.psoft_hcmss.PD_GPS_C_HRD_HDASHFW - Error while updating remote job infoScheduler.log
com.redwood.scheduler.connector.peoplesoft.job.soap.PeopleSoftSendRequest - Soap request not successfully processed
com.redwood.scheduler.api.soap.HTTPException: HTTPException (response code: 500): HTTP/1.1 500 Internal Server Error
com.redwood.scheduler.connector.peoplesoft.command.impl.JobCommand - SOAP request to peoplesoft system fails
org.xml.sax.SAXException: com.redwood.scheduler.api.soap.SOAPFaultException: SOAP-ENV:Server
StatusCode: 20
MessageID: 408:No process requests found for the process instance 6731890. (65,408)
com.redwood.scheduler.api.soap.SOAPFaultException: SOAP-ENV:Server
Comments
1 comment
This issue is fix in upcoming 2024.1.0.0 version
Please sign in to leave a comment.