Bug 778553 (SOA-1025) - Scheduling: Multiple cron schedules not supported
Summary: Scheduling: Multiple cron schedules not supported
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1025
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.2 CP02
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP03
Assignee: Len DiMaggio
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-14 17:45 UTC by Kevin Conner
Modified: 2018-11-29 20:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-11 20:11:16 UTC
Type: Bug

Attachments (Terms of Use)
jboss-esb-unfiltered.xml (2.97 KB, text/xml)
2008-12-11 20:10 UTC, Len DiMaggio 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1025 0 Major Closed Scheduling: Multiple cron schedules not supported 2012-09-18 17:39:44 UTC

Description Kevin Conner 2008-11-14 17:45:25 UTC 
Date of First Response: 2008-12-03 10:49:09
project_key: SOA

Platform issue for JBESB-2167
Comment 1 Kevin Conner 2008-11-14 17:46:19 UTC 
Link: Added: This issue depends JBESB-2167
Comment 2 Len DiMaggio 2008-12-03 15:49:09 UTC 
Assigning to QE - reporter of original linked JIRA -  for bug fix verification
Comment 3 Dana Mison 2008-12-04 08:04:54 UTC 
Release Note:

Cron schedules now use FIRE_ONCE_NOW instead of DO_NOTHING as their misfire behaviour.  This stops multiple identically timed schedules or single schedules with multiple associated listeners/jobs only ever successfully running the first scheduled item.
Comment 4 Len DiMaggio 2008-12-11 20:10:38 UTC 
Verified fixed in 4.2 CP03 CR5 - see attached jboss-esb-unfiltered.xml for an example.
Comment 5 Len DiMaggio 2008-12-11 20:10:38 UTC 
Attachment: Added: jboss-esb-unfiltered.xml
Comment 6 Len DiMaggio 2008-12-11 20:11:16 UTC 
Verified in 4.2 CP03 CR5
Comment 8 Dana Mison 2008-12-12 00:23:03 UTC 
Len: My understanding is that it was fixed in this release... so it is listed as a "resolved issue" with the note above.
Note You need to log in before you can comment on or make changes to this bug.