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

[GSS](7.4.z) WFLY-15569 - Database persistent auto timer are created twice

    XMLWordPrintable

Details

    Description

      The customer is having a cluster with two nodes in a domain setup. They have auto timer like below in @Singleton, @Startup EJBs:

      @Singleton
@Startup
public class xxx {

  @Schedule(second= "*/30", minute = "*", hour = "*", dayOfWeek = "*", month = "*", year = "*", persistent = true)
  public void schedule() {
    ...
  }

      In some cases (race condition?) the timer is created twice in the database, see attached files.

      Is this a known issue?

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-23510 [GSS](7.4.z) NPE when EJB Database Timer Persistence adjustCreateAutoTimerStatement is called

          • 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
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. WFLY-15569 Database persistent auto timer are created twice

          • 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
          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) JBEAP-23007 (7.4.z) WFLY-15583 - Adjust sql statements during initialization of DatabaseTimerPersistence

          • 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

          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) JBEAP-23008 (7.4.z) WFLY-15335 - Simplify the processing of ejb timer timeout method params

          • 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

          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) JBEAP-23009 (7.4.z) WFLY-15499 - Honor sybase as database value, and remove the unused field databaseDialects in DatabaseTimerPersistence class

          • 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

          Activity

            People

              rhn-support-ivassile Ilia Vassilev
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: