[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-2171) Incorrect timeout date calculated when schedule has a combination of non-wildcard day-of-week and non-wildcard day-of-month

[jaikiran pai (JIRA)]

     [ https://jira.jboss.org/browse/EJBTHREE-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai resolved EJBTHREE-2171.
------------------------------------

    Component Fix Version(s): timerservice-mk2:1.0.0-alpha-9
               Fix Version/s: depchain-1.0.0
                  Resolution: Done


> Incorrect timeout date calculated when schedule has a combination of non-wildcard day-of-week and non-wildcard day-of-month
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-2171
>                 URL: https://jira.jboss.org/browse/EJBTHREE-2171
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: timerservice-mk2
>    Affects Versions: depchain-1.0.0-alpha-4
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>             Fix For: depchain-1.0.0
>
>
> The EJB3.1 spec (section 18.2.1.2) says this:
> <quote>
> If dayOfMonth has a non-wildcard value and dayOfWeek has a non-wildcard value, then either the dayOfMonth field or the dayOfWeek field must match the current day (even though the other of the two fields need not match the current day).
> </quote>
> However, we currently "and" (instead of "or") the day-of-month and "day-of-week" for non-wildcard values during timeout computation. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira