Question
chennai institute of technology
IN
Last activity: 8 Apr 2024 3:06 EDT
Job schedular not force closing the first record from report results.
Job schedular getting failed with PR exception.During run time ,Its closing all the cases from reports results except the first record.Can anyone please advice on this.I have traced it but pxforcecaseclose getting failed.
I'm mentioning the error below,
Job schedular getting failed with PR exception.During run time ,Its closing all the cases from reports results except the first record.Can anyone please advice on this.I have traced it but pxforcecaseclose getting failed.
I'm mentioning the error below,
[PRException]. Exception message [-]. at com.pega.platform.executor.jobscheduler.internal.JobSchedulerProcessor.identifyUserMarkedFailure(JobSchedulerProcessor.java:155) at com.pega.platform.executor.jobscheduler.internal.JobSchedulerProcessor.execute(JobSchedulerProcessor.java:111) at com.pega.platform.executor.jobscheduler.internal.JobSchedulerProcessor.lambda$execute$0(JobSchedulerProcessor.java:92) at com.pega.platform.executor.internal.LogContextDecorator.runInDecoratedScope(LogContextDecorator.java:38) at com.pega.platform.executor.jobscheduler.internal.JobSchedulerProcessor.execute(JobSchedulerProcessor.java:90) at com.pega.platform.executor.jobscheduler.scheduler.internal.JobRunTimeImpl.execute(JobRunTimeImpl.java:104) at com.pega.platform.executor.jobscheduler.scheduler.internal.JobRunTimeDecorator.execute(JobRunTimeDecorator.java:57) at com.pega.platform.executor.jobscheduler.scheduler.internal.persistence.PersistentEligibleJobExecution.execute(PersistentEligibleJobExecution.java:51) at com.pega.platform.executor.jobscheduler.scheduler.internal.ClusterJobDecorator.run(ClusterJobDecorator.java:68) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750)
Maantic Technologies Pvt Ltd
US
Possible Causes and Solutions:
1. Access Denied for pxForceCaseClose Service:
- Verify that the Job Scheduler user has permissions to execute the pxForceCaseClose.CloseCase service. - Grant the necessary access level on the service's Access Control List (ACL).
2. Invalid or Missing Parameter Values:
- Ensure that the parameters passed to pxForceCaseClose, such as case ID or reason code, are valid and not empty. - Check the mapping between the Job Scheduler input or data page properties and the service parameters.
3. Record Locking Conflicts:
- Inspect the backend logs to see if there are any concurrent attempts to update the same case record. - Implement a locking mechanism to prevent multiple job runs from accessing the same record simultaneously.
4. Code or Data Integration Issues:
- Review the implementation of the pxForceCaseClose activity or flow to identify any potential errors or data inconsistencies. - Check whether the Job Scheduler is configured to run on the correct environment and has access to the required data sources.
5. Database Connectivity Errors:
Possible Causes and Solutions:
1. Access Denied for pxForceCaseClose Service:
- Verify that the Job Scheduler user has permissions to execute the pxForceCaseClose.CloseCase service. - Grant the necessary access level on the service's Access Control List (ACL).
2. Invalid or Missing Parameter Values:
- Ensure that the parameters passed to pxForceCaseClose, such as case ID or reason code, are valid and not empty. - Check the mapping between the Job Scheduler input or data page properties and the service parameters.
3. Record Locking Conflicts:
- Inspect the backend logs to see if there are any concurrent attempts to update the same case record. - Implement a locking mechanism to prevent multiple job runs from accessing the same record simultaneously.
4. Code or Data Integration Issues:
- Review the implementation of the pxForceCaseClose activity or flow to identify any potential errors or data inconsistencies. - Check whether the Job Scheduler is configured to run on the correct environment and has access to the required data sources.
5. Database Connectivity Errors:
- Verify that the Job Scheduler and the database it accesses are properly connected and running. - Check for any database connection timeouts or resource exhaustion issues.
6. Faulty Job Scheduler Configuration:
- Examine the Job Scheduler configuration to ensure it is set up correctly. - Check for any inconsistencies between the Job Scheduler settings and the service it is trying to execute.
Troubleshooting Steps:
1. Enable Logging: Increase the logging level for the Job Scheduler and pxForceCaseClose service to capture more detailed error messages. 2. Inspect Logs: Review the logs to identify the exact error and its context. 3. Check Permissions: Verify the access rights for the Job Scheduler user on the pxForceCaseClose service. 4. Validate Input Parameters: Check that the input parameters for pxForceCaseClose are valid and present. 5. Analyze Code: Inspect the pxForceCaseClose implementation for any potential errors or data manipulation issues. 6. Test Manually: Try executing the pxForceCaseClose service manually to isolate the problem and identify potential dependencies.
Hope it helps.
Thanks
Megha