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

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major 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

      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...

            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

              Created:
              Updated:
              Resolved: