Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10793

Canceled Timer's TimerTaskImpl not removed from ScheduledExecutorService thread pool

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.3.0.ER1
    • EAP_EWP 5.2.0
    • EJB
    • None
    • Release Notes
    • Hide
      Previous versions of JBoss EAP 5 carried a bug that, when encountered, resulted in unnecessary DEBUG messages and CPU usage. The bug presented when an EJB timer was canceled. The timer was removed from the persistence store and ceased invoking the EJB Timeout, however a TimerTaskImpl would be left in the thread pool that would continue to poll the state of the canceled timer and log DEBUG messages. This issue has been resolved in this release.
      Show
      Previous versions of JBoss EAP 5 carried a bug that, when encountered, resulted in unnecessary DEBUG messages and CPU usage. The bug presented when an EJB timer was canceled. The timer was removed from the persistence store and ceased invoking the EJB Timeout, however a TimerTaskImpl would be left in the thread pool that would continue to poll the state of the canceled timer and log DEBUG messages. This issue has been resolved in this release.
    • Documented as Resolved Issue
    • NEW

      When a EJB timer is cancelled, it no longer invokes the EJB Timeout and it is removed from the persistence store, however there is a TimerTaskImpl left in the Thread Pool, and it will continue to run and check the state (which is cancelled) and log debug messages. These should be removed as they are wasting CPU cycles.

        1. JBPAPP-10793.jar
          5 kB

              rhn-support-bmaxwell Brad Maxwell
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: