[jboss-jira] [JBoss JIRA] (WFLY-7885) Persistent calendar timer force logging for each invocation if the deployed-class has changed

[Wolf-Dieter Fink (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13349923#comment-13349923 ] 

Wolf-Dieter Fink commented on WFLY-7885:
----------------------------------------

The timer should be removed in any case if class, method or annotation/config is not longer there.

> Persistent calendar timer force logging for each invocation if the deployed-class has changed
> ---------------------------------------------------------------------------------------------
>
>                 Key: WFLY-7885
>                 URL: https://issues.jboss.org/browse/WFLY-7885
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: EJB
>            Reporter: Wolf-Dieter Fink
>            Priority: Minor
>              Labels: ejb, ejb3.1, timers, timerservice
>
> It will be common to change classes which contains @Schedule timer methods.
> In case such methods are removed or renamed (for persistent calendar timers) the server will log the following warning forever for each invocation.
>     WARN  [org.jboss.as.ejb3.timer] (EJB default - 1) WFLYEJB0161: Failed to reinstate timer 'ejb31-timer.ejb31-timer.SimpleScheduleSingletonTimerBean' (id=1a419372-d807-43d8-ac77-5be6696b022d) from its persistent state
> As this is intentional there should be a WARN message at (first) deployment time and the timer should be removed from the persistence.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)