- There are a lot of warnings in the logfile (EAP6)
WARN [org.jboss.as.ejb3] (EJB default - 8) JBAS014143: Timer 9d76bd34-ab74-409c-94a4-276dc51d5734 is still active, skipping overlapping scheduled execution at: Thu Jul 11 09:20:03 CEST 2013
- There are warnings in the logfile, since EAP6.1 the warning contains the deployment and bean information to identify the timer in addition to the unique timerId
WARN [org.jboss.as.ejb3] (EJB default - 4) JBAS014143: A previous execution of timer [EAR.JAR.SimpleTimerBean e6b7e041-8860-4347-bb0b-b8f3dca53905] is still in progress, skipping this overlapping scheduled execution at: Wed Aug 14 15:39:03 CEST 2013
- Is it possible to prevent timer from logging JBAS014143 warnings?
- I have a Stateless EJB with a method annotated with @Timeout, the timer is set to every 2 minutes. From the logs I read that if the method took more than 2 minutes the timeout method is fired again. How can I avoid new method execution until previous is finished? How the internal mechanism work in JBoss EAP? will method execution be just skipped when busy or it will be locked and put into a sort of queue with subsequent lock timeouts?
- EJB Timer timeout invocation overlapped the timeout interval and was invoked again in JBoss EAP 6, what is the cause and can this avoided?
- Red Hat JBoss Enterprise Application Platform (EAP)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.