Quartz jobs started late (WebSphere/AIX)

View: New views
3 Messages — Rating Filter:   Alert me  

Quartz jobs started late (WebSphere/AIX)

by mcnoche :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I have a scheduled job using Quartz running on WebSphere 6.1/JRE1.4.2/AIX 5.3. For some unknown reason, Quartz didn't fire the job on time, rather the job execution was delayed for a day. We checked that there was no stoppage of the WebSphere/Database in that period. Would appreciate if you experts can provide any clues or directions for trouble-shooting.

Many thanks,
Jon
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=377147&messageID=463646#463646


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: Quartz jobs started late (WebSphere/AIX)

by mcnoche :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I have faced exactly the same problem when i tried scheduling a few jobs. I faced this problem when i used the cron expression "0 16 12 ? * MON-SAT". I think there may be a problem with 12 hrs being interpreted as 00 hrs since my jobs get triggered at all other values in the hours column.
This is a very urgent requirement for us. If anyone has any clue please provide inputs.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=377147&messageID=486689#486689


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: Quartz jobs started late (WebSphere/AIX)

by mcnoche :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I apologise for the earlier post. I think my analysis was a little hasty.
I have found via trail and error that setting the start time for a trigger seems to delay the job by a day. I think quartz is intelligent enough to calculate the start time by itself based on the cron expression provided. It seems to trigger fine with start time not set at all.
Jon,hope this helps solve your problem too.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=377147&messageID=486690#486690


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...