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

Log thread information of uncompleted EJB timer task

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 16.0.0.Beta1, 16.0.0.Final
    • None
    • EJB
    • None

      WFLYEJB0043: A previous execution of timer [id=f3b0dfdb-1e94-46be-9964-69ff376fa6c0 timedObjectId=prbz-overview.prbz-overview.Aider auto-timer?:true persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@2f5b46cf initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Thu May 31 00:00:00 SGT 2018 timerState=IN_TIMEOUT info=null] is still in progress, skipping this overlapping scheduled execution at: Thu May 31 00:00:00 SGT 2018.

      Warning message WFLYEJB0043 indicates that the recurring timer is running longer than the interval, new timer is postponed. Because one App timer task worker thread is stuck there due to network connection failure.

      If the message logs more information about running threads of current timer task beyond timer id, it would be helpful to know which thread block the timer task and to allow forcibly interrupt it which is running longer than interval.

              chaowan@redhat.com Chao Wang
              chaowan@redhat.com Chao Wang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: