Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-8343

[GSS](7.1.x) Persistent calendar timer force logging for each invocation if the deployed-class has changed

    XMLWordPrintable

Details

    • Hide

      Timer can be manually removed from the persistence

      Show
      Timer can be manually removed from the persistence
    • Hide

      Deploy an EJB with a calendar timer:

      @Singleton
      public class SimpleScheduleSingletonTimerBean {
      @Schedule(second = "/10", minute = "", hour = "*")
      private void run(final Timer timer)

      { LOGGER.info("run scheduled timer"); }

      }

      After it runs rename the method "run" and deploy again.
      The timer will be started (new method)
      but the old one create a WARN message every scheduled time.

      Show
      Deploy an EJB with a calendar timer: @Singleton public class SimpleScheduleSingletonTimerBean { @Schedule(second = " /10", minute = " ", hour = "*") private void run(final Timer timer) { LOGGER.info("run scheduled timer"); } } After it runs rename the method "run" and deploy again. The timer will be started (new method) but the old one create a WARN message every scheduled time.

    Description

      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.

      Attachments

        Issue Links

          clones

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-7885 Persistent calendar timer force logging for each invocation if the deployed-class has changed

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rhn-support-iweiss Ingo Weiss
              rhn-support-wfink Wolf Fink
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: