]
Carlo de Wolf updated EJBTHREE-1330:
------------------------------------
Component/s: timerservice-mk2
(was: pool)
EJB timer service should use a thread pool to avoid OOM
-------------------------------------------------------
Key: EJBTHREE-1330
URL:
https://jira.jboss.org/jira/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: Galder ZamarreƱo
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 contact one of the administrators: