on 08-16-2013 1:36 PM
Hi All,
Recently i came across an issue where job failed with the error - " Failed to create the job in the SAP system".
Below is the log :
Failed to create the job in the SAP system
com.redwood.scheduler.api.exception.SchedulerAPIPersistenceException: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution
com.redwood.scheduler.persistence.api.PersistenceException$ModelModificationVetoException: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution
java.lang.NullPointerException: null
JCS-122035: Unable to persist: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution.
Please let me know what could be the cause for this issue and is there any fix.
thanks in advance.
Regards,
KN
Hi Kartik,
A shot in the dark... I faced a similar issue for a job for which I was modifying the batch job definition and it was submitted at the same instant by the recurrence.
First run failed with persistence error and further runs were successful. If this is not the case, Please ignore the post
Cheers,
Aswin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi KN,
A java.lang.NullPointerException (NPE) is a bug in the software. There should be a better error message. Do you have any operator messages from around that time?
What kind of job was this ? Was the SAP system available and did other jobs run around that time on that system ? Did you submit this job or was it intercepted ?
I would use the 'Get Support Files' action on the job and create an OSS ticket. Also provide the defaut trace for around the time the job ran.
Hope this helps, sorry I cannot pinpoint exactly what the issue is.
HP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
Thanks for the response.
There is no operator messages recorded for this failure.
its an ECC job chain, system was available during the job execution and its scheduled to run every hour.
later runs of the same job chain completed successfully.
as suggested i will try get support files related the failed job chain.
Regards,
KN
User | Count |
---|---|
70 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.