Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rundeck jobs fail to execute sometimes #193

Closed
sharadr opened this issue Jul 18, 2012 · 3 comments
Closed

Rundeck jobs fail to execute sometimes #193

sharadr opened this issue Jul 18, 2012 · 3 comments
Assignees
Labels
Milestone

Comments

@sharadr
Copy link

sharadr commented Jul 18, 2012

Environment:
Rundeck 1.4.4-dev connected to Oracle.

The job dispatch "hangs" with no output to the console.

In the catalina.out , the following error appears:
ERROR: Unable to start Job execution: failed to lookup Exception object from job data map: id: 497
java.lang.RuntimeException: failed to lookup Exception object from job data map: id: 497
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77)
at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:71)
at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:81)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:52)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:190)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:198)
at ExecutionJob.initialize(ExecutionJob.groovy:138)
at ExecutionJob$initialize.callCurrent(Unknown Source)
at ExecutionJob.execute(ExecutionJob.groovy:38)
at org.quartz.core.JobRunShell.run(JobRunShell.java:199)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546)

After discussing with greg,:

There is a race condition when starting a job. the execution is created, but not flushed to the DB when the processing thread starts, so it fails to find it

@gschueler
Copy link
Member

ref commit c91d7e0

@mvam75
Copy link

mvam75 commented Aug 20, 2012

This happens with MySQL on 1.4.3 as well.

@gschueler
Copy link
Member

I wasn't able to reproduce with mysql, but I confirmed the issue appears fixed for Oracle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants