Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-4967

RequestController drops queued tasks randomly during server start.

    Details

    • Type: Bug
    • Status: Pull Request Sent (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 11.0.0.Final
    • Fix Version/s: None
    • Component/s: Server
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      I created a minimal example project which demonstrates this EJB timer issue: https://github.com/guestlinelabs/wildfly-timer-issue

      Recreation steps

      1. Deploy sample application to the wildfly server (via cli or just by copy it to standalone/deployments).
      2. Start the server
      Note

      Above order is very important because when app is deployed after RequestController is resumed, issue is not occurring.

      Expected

      All timers from SomeTimers class are triggered after the server is resumed.

      This can be confirmed by finding an entry in server log at INFO level, which message starts with timers OK

      Incorrect behaviour

      Some (random) timers are omitted, there is a message in logs saying timers FAIL or there is no log entry at all.

      Show
      I created a minimal example project which demonstrates this EJB timer issue: https://github.com/guestlinelabs/wildfly-timer-issue Recreation steps Deploy sample application to the wildfly server (via cli or just by copy it to standalone/deployments). Start the server Note Above order is very important because when app is deployed after RequestController is resumed, issue is not occurring. Expected All timers from SomeTimers class are triggered after the server is resumed. This can be confirmed by finding an entry in server log at INFO level, which message starts with timers OK Incorrect behaviour Some (random) timers are omitted, there is a message in logs saying timers FAIL or there is no log entry at all.
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Only for `@Schedulled` timers.
      suspend() then activate() timer trough cli.

      Show
      Only for `@Schedulled` timers. suspend() then activate() timer trough cli.

      Description

      Our deployment is quite complex, EAR app containing several modules.
      After move to different data-center some of EJB timers will not be triggered at all after server restart (randomly).

      There was no change to wildfly server version and application itself.
      Only hardware/network changed and issue started occurring.

      Classified as : WEIRDO and some race conditions was assumed.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jmesnil Jeff Mesnil
                Reporter:
                khroolick P K
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: