Quartz job stops executing on StaleObjectStateException exception

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Quartz job stops executing on StaleObjectStateException exception

fabiano taioli
Hi.

I have a problem with quartz ( plugin :quartz2:2.1.6.2 but I have test even with plugin :quartz:1.0-RC7 but the problem does not change) on my Grails Project ( grails 2.2.1 ).

I have a job like this

class MyJob {

def concurrent = false

def execute(context){

        try {

            //....
            // works with domains .....
            myDomain.save(flush: true)
            // works with domains .....
            //....

            sessionFactory.currentSession.flush()

        } catch (org.springframework.dao.OptimisticLockingFailureException olfe) {
            println "Job failed by database exception "
        } catch ( org.springframework.orm.hibernate3.HibernateOptimisticLockingFailureException ole){
            println "Job failed by database exception "
        } catch ( org.hibernate.HibernateException hibe ){
            println "Job failed by database exception "
        }
    }

}

}

Sometimes a StaleObjectStateException occour in the execute method. This is ok for my logic, I'm using grails optimistic locking and this exceptions occour only once a week.

The problem is when this exceptions occour the Job stops to fire again.

I have tried co wrap the method code in a try catch and flush hibernate session inside to capture the exception but without fortune. The exception is not capture by any of my catchs.

Looking online I found this an old grails quartz bug but it's fixed, and in any case using the try{}catch must bypass the bug.

P.S. The job is scheduled from bootstrab by a call of this type

MyJob.schedule( 10000L )

The exception that stops the scheduling is

[194949896] core.ErrorLogger Unable to notify JobListener(s) of Job that was executed: (error will be ignored). trigger= DEFAULT.MT_3tbn6lewgiqa3 job= DEFAULT.MyJob
org.quartz.SchedulerException: JobListener 'persistenceContextJobListener' threw exception: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [MyDomain#42] [See nested exception: org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [MyDomain#42]]
    at org.quartz.core.QuartzScheduler.notifyJobListenersWasExecuted(QuartzScheduler.java:1939)
    at org.quartz.core.JobRunShell.notifyJobListenersComplete(JobRunShell.java:361)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:235)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
Caused by: org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [MyDomain#42]
    at grails.plugin.quartz2.PersistenceContextJobListener.jobWasExecuted(PersistenceContextJobListener.groovy:46)
    at org.quartz.core.QuartzScheduler.notifyJobListenersWasExecuted(QuartzScheduler.java:1937)
    ... 3 more

.....

events.PatchedDefaultFlushEventListener Could not synchronize database state with session
org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [MyJob#42]
    at MyJob.execute(MyJob.groovy:354)
    at grails.plugin.quartz2.GrailsArtefactJob.execute(GrailsArtefactJob.java:57)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)


P.S. StackOverflow question

Fabiano Taioli

Vista Tecnologie
www.vista.it
Reply | Threaded
Open this post in threaded view
|

RE: Quartz job stops executing on StaleObjectStateException exception

Ryan Vanderwerf
Are you putting a hibernate object directly into the job details class for the job on launch or is there some code we can't see that queries it then updates it then fails? If not the latter,  you want to put the object id in the map I stead, query it during runtime, then update (and handle optimistic locking appropriately).

Ryan



-------- Original message --------
From: fabiano taioli <[hidden email]>
Date: 05/06/2013 3:01 AM (GMT-06:00)
To: [hidden email]
Subject: [grails-user] Quartz job stops executing on StaleObjectStateException exception


Hi.

I have a problem with quartz ( plugin :quartz2:2.1.6.2 but I have test even
with plugin :quartz:1.0-RC7 but the problem does not change) on my Grails
Project ( grails 2.2.1 ).

I have a job like this

class MyJob {

def concurrent = false

def execute(context){

        try {

            //....
            // works with domains .....
            myDomain.save(flush: true)
            // works with domains .....
            //....

            sessionFactory.currentSession.flush()

        } catch (org.springframework.dao.OptimisticLockingFailureException
olfe) {
            println "Job failed by database exception "
        } catch (
org.springframework.orm.hibernate3.HibernateOptimisticLockingFailureException
ole){
            println "Job failed by database exception "
        } catch ( org.hibernate.HibernateException hibe ){
            println "Job failed by database exception "
        }
    }

}

}

Sometimes a StaleObjectStateException occour in the execute method. This is
ok for my logic, I'm using grails optimistic locking and this exceptions
occour only once a week.

The problem is when this exceptions occour the Job stops to fire again.

I have tried co wrap the method code in a try catch and flush hibernate
session inside to capture the exception but without fortune. The exception
is not capture by any of my catchs.

Looking online I found this an old grails quartz bug but it's fixed, and in
any case using the try{}catch must bypass the bug.

P.S. The job is scheduled from bootstrab by a call of this type

MyJob.schedule( 10000L )

The exception that stops the scheduling is

[194949896] core.ErrorLogger Unable to notify JobListener(s) of Job that was
executed: (error will be ignored). trigger= DEFAULT.MT_3tbn6lewgiqa3 job=
DEFAULT.MyJob
org.quartz.SchedulerException: JobListener 'persistenceContextJobListener'
threw exception: Row was updated or deleted by another transaction (or
unsaved-value mapping was incorrect): [MyDomain#42] [See nested exception:
org.hibernate.StaleObjectStateException: Row was updated or deleted by
another transaction (or unsaved-value mapping was incorrect): [MyDomain#42]]
    at
org.quartz.core.QuartzScheduler.notifyJobListenersWasExecuted(QuartzScheduler.java:1939)
    at
org.quartz.core.JobRunShell.notifyJobListenersComplete(JobRunShell.java:361)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:235)
    at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
Caused by: org.hibernate.StaleObjectStateException: Row was updated or
deleted by another transaction (or unsaved-value mapping was incorrect):
[MyDomain#42]
    at
grails.plugin.quartz2.PersistenceContextJobListener.jobWasExecuted(PersistenceContextJobListener.groovy:46)
    at
org.quartz.core.QuartzScheduler.notifyJobListenersWasExecuted(QuartzScheduler.java:1937)
    ... 3 more

.....

events.PatchedDefaultFlushEventListener Could not synchronize database state
with session
org.hibernate.StaleObjectStateException: Row was updated or deleted by
another transaction (or unsaved-value mapping was incorrect): [MyJob#42]
    at MyJob.execute(MyJob.groovy:354)
    at
grails.plugin.quartz2.GrailsArtefactJob.execute(GrailsArtefactJob.java:57)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
    at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)


P.S.  StackOverflow question
<http://stackoverflow.com/questions/16394437/quartz-job-stops-executing-on-staleobjectstateexception-exception





-----
Fabiano Taioli

Vista Tecnologie
www.vista.it

--
View this message in context: http://grails.1312388.n4.nabble.com/Quartz-job-stops-executing-on-StaleObjectStateException-exception-tp4644372.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Quartz job stops executing on StaleObjectStateException exception

fabiano taioli
Thank you Ryan,

No there is no object in the map. The domain objects are loaded inside the try {} catch of the execute method .

How I can handle optimistic locking ? How I can capture the exceptions to be sure the job never stops!?

Thank you

On 06/05/13 13:48, Ryan Vanderwerf [via Grails] wrote:
Are you putting a hibernate object directly into the job details class for the job on launch or is there some code we can't see that queries it then updates it then fails? If not the latter,  you want to put the object id in the map I stead, query it during runtime, then update (and handle optimistic locking appropriately).

Ryan



-------- Original message --------
From: fabiano taioli <[hidden email]>
Date: 05/06/2013 3:01 AM (GMT-06:00)
To: [hidden email]
Subject: [grails-user] Quartz job stops executing on StaleObjectStateException exception


Hi.

I have a problem with quartz ( plugin :quartz2:2.1.6.2 but I have test even
with plugin :quartz:1.0-RC7 but the problem does not change) on my Grails
Project ( grails 2.2.1 ).

I have a job like this

class MyJob {

def concurrent = false

def execute(context){

        try {

            //....
            // works with domains .....
            myDomain.save(flush: true)
            // works with domains .....
            //....

            sessionFactory.currentSession.flush()

        } catch (org.springframework.dao.OptimisticLockingFailureException
olfe) {
            println "Job failed by database exception "
        } catch (
org.springframework.orm.hibernate3.HibernateOptimisticLockingFailureException
ole){
            println "Job failed by database exception "
        } catch ( org.hibernate.HibernateException hibe ){
            println "Job failed by database exception "
        }
    }

}

}

Sometimes a StaleObjectStateException occour in the execute method. This is
ok for my logic, I'm using grails optimistic locking and this exceptions
occour only once a week.

The problem is when this exceptions occour the Job stops to fire again.

I have tried co wrap the method code in a try catch and flush hibernate
session inside to capture the exception but without fortune. The exception
is not capture by any of my catchs.

Looking online I found this an old grails quartz bug but it's fixed, and in
any case using the try{}catch must bypass the bug.

P.S. The job is scheduled from bootstrab by a call of this type

MyJob.schedule( 10000L )

The exception that stops the scheduling is

[194949896] core.ErrorLogger Unable to notify JobListener(s) of Job that was
executed: (error will be ignored). trigger= DEFAULT.MT_3tbn6lewgiqa3 job=
DEFAULT.MyJob
org.quartz.SchedulerException: JobListener 'persistenceContextJobListener'
threw exception: Row was updated or deleted by another transaction (or
unsaved-value mapping was incorrect): [MyDomain#42] [See nested exception:
org.hibernate.StaleObjectStateException: Row was updated or deleted by
another transaction (or unsaved-value mapping was incorrect): [MyDomain#42]]
    at
org.quartz.core.QuartzScheduler.notifyJobListenersWasExecuted(QuartzScheduler.java:1939)
    at
org.quartz.core.JobRunShell.notifyJobListenersComplete(JobRunShell.java:361)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:235)
    at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
Caused by: org.hibernate.StaleObjectStateException: Row was updated or
deleted by another transaction (or unsaved-value mapping was incorrect):
[MyDomain#42]
    at
grails.plugin.quartz2.PersistenceContextJobListener.jobWasExecuted(PersistenceContextJobListener.groovy:46)
    at
org.quartz.core.QuartzScheduler.notifyJobListenersWasExecuted(QuartzScheduler.java:1937)
    ... 3 more

.....

events.PatchedDefaultFlushEventListener Could not synchronize database state
with session
org.hibernate.StaleObjectStateException: Row was updated or deleted by
another transaction (or unsaved-value mapping was incorrect): [MyJob#42]
    at MyJob.execute(MyJob.groovy:354)
    at
grails.plugin.quartz2.GrailsArtefactJob.execute(GrailsArtefactJob.java:57)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
    at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)


P.S.  StackOverflow question
<http://stackoverflow.com/questions/16394437/quartz-job-stops-executing-on-staleobjectstateexception-exception





-----
Fabiano Taioli

Vista Tecnologie
www.vista.it

--
View this message in context: http://grails.1312388.n4.nabble.com/Quartz-job-stops-executing-on-StaleObjectStateException-exception-tp4644372.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email





To unsubscribe from Quartz job stops executing on StaleObjectStateException exception, click here.
NAML

Fabiano Taioli

Vista Tecnologie
www.vista.it
Reply | Threaded
Open this post in threaded view
|

Re: Quartz job stops executing on StaleObjectStateException exception

Stefan Rother-2
Hello,
my way to approach this is to 
a) move the code inside the try block of execute() into a service method, 
b) lock the domain class before modifying it (in this case MyDomain) and
c) catch Exception after all other types of exceptions have been caught. 
It will not prevent all kinds of StaleObjectStateExceptions but it should lessen them. 

And d) even if concurrent is set to false it may be called parallel to other code (e.g. a service method from your normal application or even in a second web server running your application).
If any other process  tries to save the same MyDomain instance at the same time as the service does, it could provoke StaleObjectStateExceptions.
Because then this instance exists two in the Hibernate session of the job and in the Hibernate session of the other process at the same time. The process which tries first to save the domain object wins and the other one loses and throws a StaleObjectStateException.

Stefan


Am 06.05.2013 um 14:26 schrieb fabiano taioli <[hidden email]>:

Thank you Ryan,

No there is no object in the map. The domain objects are loaded inside the try {} catch of the execute method .

How I can handle optimistic locking ? How I can capture the exceptions to be sure the job never stops!?

Thank you

On 06/05/13 13:48, Ryan Vanderwerf [via Grails] wrote:
Are you putting a hibernate object directly into the job details class for the job on launch or is there some code we can't see that queries it then updates it then fails? If not the latter,  you want to put the object id in the map I stead, query it during runtime, then update (and handle optimistic locking appropriately).

Ryan



-------- Original message --------
From: fabiano taioli <<a moz-do-not-send="true" href="x-msg://120/user/SendEmail.jtp?type=node&amp;node=4644383&amp;i=0" target="_top" rel="nofollow" link="external">[hidden email]>
Date: 05/06/2013 3:01 AM (GMT-06:00)
To: <a moz-do-not-send="true" href="x-msg://120/user/SendEmail.jtp?type=node&amp;node=4644383&amp;i=1" target="_top" rel="nofollow" link="external">[hidden email]
Subject: [grails-user] Quartz job stops executing on StaleObjectStateException exception


Hi.

I have a problem with quartz ( plugin :quartz2:2.1.6.2 but I have test even
with plugin :quartz:1.0-RC7 but the problem does not change) on my Grails
Project ( grails 2.2.1 ).

I have a job like this

class MyJob {

def concurrent = false

def execute(context){

        try {

            //....
            // works with domains .....
            myDomain.save(flush: true)
            // works with domains .....
            //....

            sessionFactory.currentSession.flush()

        } catch (org.springframework.dao.OptimisticLockingFailureException
olfe) {
            println "Job failed by database exception "
        } catch (
org.springframework.orm.hibernate3.HibernateOptimisticLockingFailureException
ole){
            println "Job failed by database exception "
        } catch ( org.hibernate.HibernateException hibe ){
            println "Job failed by database exception "
        }
    }

}

}

Sometimes a StaleObjectStateException occour in the execute method. This is
ok for my logic, I'm using grails optimistic locking and this exceptions
occour only once a week.

The problem is when this exceptions occour the Job stops to fire again.

I have tried co wrap the method code in a try catch and flush hibernate
session inside to capture the exception but without fortune. The exception
is not capture by any of my catchs.

Looking online I found this an old grails quartz bug but it's fixed, and in
any case using the try{}catch must bypass the bug.

P.S. The job is scheduled from bootstrab by a call of this type

MyJob.schedule( 10000L )

The exception that stops the scheduling is

[194949896] core.ErrorLogger Unable to notify JobListener(s) of Job that was
executed: (error will be ignored). trigger= DEFAULT.MT_3tbn6lewgiqa3 job=
DEFAULT.MyJob
org.quartz.SchedulerException: JobListener 'persistenceContextJobListener'
threw exception: Row was updated or deleted by another transaction (or
unsaved-value mapping was incorrect): [MyDomain#42] [See nested exception:
org.hibernate.StaleObjectStateException: Row was updated or deleted by
another transaction (or unsaved-value mapping was incorrect): [MyDomain#42]]
    at
org.quartz.core.QuartzScheduler.notifyJobListenersWasExecuted(QuartzScheduler.java:1939)
    at
org.quartz.core.JobRunShell.notifyJobListenersComplete(JobRunShell.java:361)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:235)
    at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
Caused by: org.hibernate.StaleObjectStateException: Row was updated or
deleted by another transaction (or unsaved-value mapping was incorrect):
[MyDomain#42]
    at
grails.plugin.quartz2.PersistenceContextJobListener.jobWasExecuted(PersistenceContextJobListener.groovy:46)
    at
org.quartz.core.QuartzScheduler.notifyJobListenersWasExecuted(QuartzScheduler.java:1937)
    ... 3 more

.....

events.PatchedDefaultFlushEventListener Could not synchronize database state
with session
org.hibernate.StaleObjectStateException: Row was updated or deleted by
another transaction (or unsaved-value mapping was incorrect): [MyJob#42]
    at MyJob.execute(MyJob.groovy:354)
    at
grails.plugin.quartz2.GrailsArtefactJob.execute(GrailsArtefactJob.java:57)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
    at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)


P.S.  StackOverflow question
<http://stackoverflow.com/questions/16394437/quartz-job-stops-executing-on-staleobjectstateexception-exception





-----
Fabiano Taioli

Vista Tecnologie
www.vista.it

--
View this message in context: http://grails.1312388.n4.nabble.com/Quartz-job-stops-executing-on-StaleObjectStateException-exception-tp4644372.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email





To unsubscribe from Quartz job stops executing on StaleObjectStateException exception, <a moz-do-not-send="true" href="x-msg://120/" target="_top" rel="nofollow" link="external">click here.
NAML

Fabiano Taioli

Vista Tecnologie
www.vista.it


View this message in context: Re: Quartz job stops executing on StaleObjectStateException exception
Sent from the Grails - user mailing list archive at Nabble.com.

Reply | Threaded
Open this post in threaded view
|

Re: Quartz job stops executing on StaleObjectStateException exception

fabiano taioli
Hi Stefan,

My problem is not the StaleObjectStateExceptions, if it occour and the job fails that run it's not a problem.

My problem is that when StaleObjectStateExceptions occour the job scheduling stops and the Job is never re-run until I restart
the APP.

Thank you
Fabiano

On 07/05/13 09:11, Stefan Rother-2 [via Grails] wrote:
Hello,
my way to approach this is to 
a) move the code inside the try block of execute() into a service method, 
b) lock the domain class before modifying it (in this case MyDomain) and
c) catch Exception after all other types of exceptions have been caught. 
It will not prevent all kinds of StaleObjectStateExceptions but it should lessen them. 

And d) even if concurrent is set to false it may be called parallel to other code (e.g. a service method from your normal application or even in a second web server running your application).
If any other process  tries to save the same MyDomain instance at the same time as the service does, it could provoke StaleObjectStateExceptions.
Because then this instance exists two in the Hibernate session of the job and in the Hibernate session of the other process at the same time. The process which tries first to save the domain object wins and the other one loses and throws a StaleObjectStateException.

Stefan


Am 06.05.2013 um 14:26 schrieb fabiano taioli <[hidden email]>:

Thank you Ryan,

No there is no object in the map. The domain objects are loaded inside the try {} catch of the execute method .

How I can handle optimistic locking ? How I can capture the exceptions to be sure the job never stops!?

Thank you

On 06/05/13 13:48, Ryan Vanderwerf [via Grails] wrote:
Are you putting a hibernate object directly into the job details class for the job on launch or is there some code we can't see that queries it then updates it then fails? If not the latter,  you want to put the object id in the map I stead, query it during runtime, then update (and handle optimistic locking appropriately).

Ryan



-------- Original message --------
From: fabiano taioli <<a moz-do-not-send="true" href="x-msg://120/user/SendEmail.jtp?type=node&amp;node=4644383&amp;i=0" target="_top" rel="nofollow" link="external">[hidden email]>
Date: 05/06/2013 3:01 AM (GMT-06:00)
To: <a moz-do-not-send="true" href="x-msg://120/user/SendEmail.jtp?type=node&amp;node=4644383&amp;i=1" target="_top" rel="nofollow" link="external">[hidden email]
Subject: [grails-user] Quartz job stops executing on StaleObjectStateException exception


Hi.

I have a problem with quartz ( plugin :quartz2:2.1.6.2 but I have test even
with plugin :quartz:1.0-RC7 but the problem does not change) on my Grails
Project ( grails 2.2.1 ).

I have a job like this

class MyJob {

def concurrent = false

def execute(context){

        try {

            //....
            // works with domains .....
            myDomain.save(flush: true)
            // works with domains .....
            //....

            sessionFactory.currentSession.flush()

        } catch (org.springframework.dao.OptimisticLockingFailureException
olfe) {
            println "Job failed by database exception "
        } catch (
org.springframework.orm.hibernate3.HibernateOptimisticLockingFailureException
ole){
            println "Job failed by database exception "
        } catch ( org.hibernate.HibernateException hibe ){
            println "Job failed by database exception "
        }
    }

}

}

Sometimes a StaleObjectStateException occour in the execute method. This is
ok for my logic, I'm using grails optimistic locking and this exceptions
occour only once a week.

The problem is when this exceptions occour the Job stops to fire again.

I have tried co wrap the method code in a try catch and flush hibernate
session inside to capture the exception but without fortune. The exception
is not capture by any of my catchs.

Looking online I found this an old grails quartz bug but it's fixed, and in
any case using the try{}catch must bypass the bug.

P.S. The job is scheduled from bootstrab by a call of this type

MyJob.schedule( 10000L )

The exception that stops the scheduling is

[194949896] core.ErrorLogger Unable to notify JobListener(s) of Job that was
executed: (error will be ignored). trigger= DEFAULT.MT_3tbn6lewgiqa3 job=
DEFAULT.MyJob
org.quartz.SchedulerException: JobListener 'persistenceContextJobListener'
threw exception: Row was updated or deleted by another transaction (or
unsaved-value mapping was incorrect): [MyDomain#42] [See nested exception:
org.hibernate.StaleObjectStateException: Row was updated or deleted by
another transaction (or unsaved-value mapping was incorrect): [MyDomain#42]]
    at
org.quartz.core.QuartzScheduler.notifyJobListenersWasExecuted(QuartzScheduler.java:1939)
    at
org.quartz.core.JobRunShell.notifyJobListenersComplete(JobRunShell.java:361)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:235)
    at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
Caused by: org.hibernate.StaleObjectStateException: Row was updated or
deleted by another transaction (or unsaved-value mapping was incorrect):
[MyDomain#42]
    at
grails.plugin.quartz2.PersistenceContextJobListener.jobWasExecuted(PersistenceContextJobListener.groovy:46)
    at
org.quartz.core.QuartzScheduler.notifyJobListenersWasExecuted(QuartzScheduler.java:1937)
    ... 3 more

.....

events.PatchedDefaultFlushEventListener Could not synchronize database state
with session
org.hibernate.StaleObjectStateException: Row was updated or deleted by
another transaction (or unsaved-value mapping was incorrect): [MyJob#42]
    at MyJob.execute(MyJob.groovy:354)
    at
grails.plugin.quartz2.GrailsArtefactJob.execute(GrailsArtefactJob.java:57)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
    at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)


P.S.  StackOverflow question
<http://stackoverflow.com/questions/16394437/quartz-job-stops-executing-on-staleobjectstateexception-exception





-----
Fabiano Taioli

Vista Tecnologie
www.vista.it

--
View this message in context: http://grails.1312388.n4.nabble.com/Quartz-job-stops-executing-on-StaleObjectStateException-exception-tp4644372.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email





To unsubscribe from Quartz job stops executing on StaleObjectStateException exception, <a moz-do-not-send="true" href="x-msg://120/" target="_top" rel="nofollow" link="external">click here.
NAML

Fabiano Taioli

Vista Tecnologie
www.vista.it


View this message in context: Re: Quartz job stops executing on StaleObjectStateException exception
Sent from the Grails - user mailing list archive at Nabble.com.




To unsubscribe from Quartz job stops executing on StaleObjectStateException exception, click here.
NAML

Fabiano Taioli

Vista Tecnologie
www.vista.it
Reply | Threaded
Open this post in threaded view
|

Re: Quartz job stops executing on StaleObjectStateException exception

crow131
Hi Fabiano,

Did you figure this one out with the quartz 2:2.1.6.2 issue. I have run into the same problem?

Kevin