Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-17012

Created timer will random skipped due to "Timer is not active"

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 27.0.0.Final
    • 26.1.1.Final, 26.1.2.Final
    • EJB

    Description

      After we upgrade Wildfly from 26.1.0 to 26.1.2, I found our cases not stable, sometimes the created timer will skipped and found below log:

      01:24:42.976 DEBUG [org.jboss.as.ejb3.timer] (EJB default - 2) Timer is not active, skipping this scheduled execution at: Fri Sep 16 01:24:42 UTC 2022for [id=8c7ce6d9-351c-458e-8e49-ff938a5e8b96 timedObjectId=abcdefg auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@176cec24 previousRun=null initialExpiration=Fri Sep 16 01:24:42 UTC 2022 intervalDuration(in milli sec)=0 nextExpiration=Fri Sep 16 01:24:42 UTC 2022 timerState=ACTIVE info=abcdefg@2b937c98]

      And from the release notes I found maybe below changes impact this timer logic.

      https://github.com/wildfly/wildfly/pull/15463

      Please double check it, thanks.

      Attachments

        Issue Links

          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-23981 [GSS](7.4.z) Created timer will random skipped due to "Timer is not active"

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is related to

          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-16298 Improve performance related to TimerServiceImpl#scheduledTimerFutures

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              cfang@redhat.com Cheng Fang
              liying.zhou.pf Liying Zhou
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: