]
Brian Stansberry updated WFLY-10542:
------------------------------------
Issue Type: Enhancement (was: Feature Request)
Log thread information of uncompleted EJB timer task
-----------------------------------------------------
Key: WFLY-10542
URL:
https://issues.jboss.org/browse/WFLY-10542
Project: WildFly
Issue Type: Enhancement
Components: EJB
Reporter: Chao Wang
Assignee: Chao Wang
Priority: Major
{quote}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.{quote}
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.