History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QUARTZ-521
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: James House
Reporter: Holger Bruch
Votes: 0
Watchers: 1
Operations

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

(reopen) RAMJobStore Trigger deletion infinite loop in acquireNextTrigger

Created: 22/Oct/06 02:48 AM   Updated: 21/Oct/07 02:02 PM
Component/s: Job Stores
Affects Version/s: 1.5.2
Fix Version/s: 1.6.1

File Attachments: 1. Text File RAMJobStore.patch (0.7 kb)

Environment: jdk 1.5.0_07 on windows xp

Flags: Patch


 Description  « Hide
(I'm reposting issue QUARTZ-106 here, since I cannot see how to re-open an issue in opensymphony JIRA).

As described in QUARTZ-106, the trigger returned by timeTriggers.first() can't be removed, since it's nextFireTime is set to null. If I'm right, RAMJobStore.triggerFired supposes the acquired trigger to be removed from the timeTriggers tree set. This might not hold true, if the trigger was replaced between acquiring and triggering, since the new trigger is added to timeTriggers.

To be sure that the fired trigger is not contained in timeTriggers, the attached patch removes it's TriggerWrapper before calculating it's next fire time.


 All   Comments   Change History      Sort Order:
Henri Yandell - [30/Apr/07 06:50 PM ]
This makes sense to me.

James House - [21/Oct/07 02:02 PM ]
applied patch.