[
https://issues.jboss.org/browse/EJBTHREE-1330?page=com.atlassian.jira.plu...
]
Gabriele Contini commented on EJBTHREE-1330:
--------------------------------------------
Hi, I'm experiencing a similar issue on jboss 5.1.0GA.
As discussed in
http://community.jboss.org/message/366436 the proposed workaround seem not
working. Also seem that org.jboss.ejb3.timerservice.quartz.QuartzTimerServiceFactory
isn't available anymore in this version of the AS.
Jboss 6 resolves this issue.
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: 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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira