History | Log In     View a printable version of the current page.  
   HOME       BROWSE PROJECT       FIND ISSUES   
    QUICK SEARCH:  
Issue Details (XML | Word | Printable)

Key: QUARTZ-19
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: James House
Reporter: James House
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Quartz Scheduler

Don't start misfire handling until scheduler.start() has been invoked

Created: 03/Jun/04 04:38 PM   Updated: 27/May/05 10:02 PM
Component/s: Core, Job Stores
Affects Version/s: 1.5
Fix Version/s: 1.5


 Description  « Hide

Misfire handling currently gets kicked off by the call to JobStoreSupport.initialize(..)

this makes schedFactory.getScheduler(..) take a long time...

 All   Comments   Change History      Sort Order:
[ Permlink | « Hide ]
James House - [28/Jun/04 11:20 PM ]
related, but opposite: http://jira.opensymphony.com/browse/QUARTZ-35

[ Permlink | « Hide ]
James House - [27/May/05 10:02 PM ]

Now the call to scheduler.start() performs these actions (cleaning up volatile triggers & jobs, and kicking off job recovery).


Powered by a free Atlassian JIRA non-profit license for OpenSymphony. Try JIRA - bug tracking software for your team.
Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.8-#209) - Bug/feature request - Contact Administrators