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

Persistent EJB timer timed_object_id naming discrepancy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • None
    • 12.0.0.Final
    • EJB
    • None

      Persistent EJB timers created declaratively (with @Schedule) create timed_object_id without version information while timers created using TimerService API include version info from deployment unit.

      This way after version upgrade @Schedule timers survive but TimerService API created ones are lost and need to be created again.
      I also seems that old timers remain created or at least their definitions can be seen in jboss_ejb_timer table.

              lvydra Lukas Vydra
              boris.pran Boris Pran (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: