[jboss-jira] [JBoss JIRA] (EJBTHREE-1330) EJB timer service should use a thread pool to avoid OOM
[
https://issues.jboss.org/browse/EJBTHREE-1330?page=com.atlassian.jira.plu...
]
Carlo de Wolf commented on EJBTHREE-1330:
-----------------------------------------
This issue is reported against a version which is no longer maintained, which means that
it will not receive a fix. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of JBoss Application
Server please feel free to open a bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
EJB timer service should use a thread pool to avoid OOM
-------------------------------------------------------
Key: EJBTHREE-1330
URL: https://issues.jboss.org/browse/EJBTHREE-1330
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Affects Versions: AS 4.2.2.GA, AS 5.0.0.Beta4
Reporter: Galder Zamarreño
Assignee: Carlo de Wolf
Priority: Minor
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira