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

Use GPS Developed Fix for EJBTHREE-1330 [EJB timer service should use a thread pool to avoid OOM]

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.2.0
    • EAP_EWP 5.1.1, EAP_EWP 5.1.2
    • EJB
    • None
    • Release Notes
    • Hide
      Extensive use of the ejbTimeout() callbacks in an EJB resulted in "failure to create native thread" OOM (out of memory) errors rendering the server unusable. Now, each server has a ScheduledExecutorService, which registers any deployed EJB. The service has a restricted pool size of threads which process the timeout callbacks. The pool size is set to 50 threads by default.
      Show
      Extensive use of the ejbTimeout() callbacks in an EJB resulted in "failure to create native thread" OOM (out of memory) errors rendering the server unusable. Now, each server has a ScheduledExecutorService, which registers any deployed EJB. The service has a restricted pool size of threads which process the timeout callbacks. The pool size is set to 50 threads by default.
    • Documented as Resolved Issue
    • NEW

    Description

      See EJBTHREE-1330 for more information.

      Use of many (thousands) EJB timers results in "failure to create native thread" problems.

      GPS worked with this customer to create a custom implementation to avoid this. The custom implementation has tests, etc, and can be deployed side-by-side with the old implementation so there is no backwards compatibility issue.

      The customer is using this on EAP 5, and would like us to fully support it (or some version of it) in the 5.x future...

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-10793 Canceled Timer's TimerTaskImpl not removed from ScheduledExecutorService thread pool

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. EJBTHREE-1330 EJB timer service should use a thread pool to avoid OOM

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

              rhn-engineering-cdewolf Carlo de Wolf
              bgeorges@redhat.com Bruno Georges
              Eva Kopalova Eva Kopalova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: