Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-1330

EJB timer service should use a thread pool to avoid OOM

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Minor
    • None
    • AS 4.2.2.GA, AS 5.0.0.Beta4
    • timerservice-mk2
    • None
    • Workaround Exists
    • Hide

      Use org.jboss.ejb3.StrictMaxPool instead of org.jboss.ejb3.ThreadlocalPool.
      This will limit the total number of instances in the VM is limited to the maximum
      pool size and the OOM will not occur.

      Show
      Use org.jboss.ejb3.StrictMaxPool instead of org.jboss.ejb3.ThreadlocalPool. This will limit the total number of instances in the VM is limited to the maximum pool size and the OOM will not occur.
    • Medium

    Description

      The default EJB timer service used by the EJB3 layer is based on
      org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory which delegates
      to the standard org.jboss.ejb.txtimer.EJBTimerService.

      For EJB3 beans using the EJB timer service the thread local pool should not be used.
      Since the current EJB timer service creates a new thread for each timer being created, the
      thread local pool will create a matching instance of the bean for that thread. Thus the number
      of active instances in total can effectively grow unchecked and thus an OOM will occur.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-1938 EJB timer pool has problems with OOME and workaround does too.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-8035 Use GPS Developed Fix for EJBTHREE-1330 [EJB timer service should use a thread pool to avoid OOM]

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. EJBTHREE-1175 ThreadlocalPool does not remove active BeanContext instances from InfinitePool

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Activity

            People

              rhn-engineering-cdewolf Carlo de Wolf
              rh-ee-galder Galder Zamarreño
              Votes:
              7 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: