-
Bug
-
Resolution: Done
-
Major
-
EAP_EWP 5.1.1, EAP_EWP 5.1.2
-
None
-
Release Notes
-
-
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...
- is related to
-
JBPAPP-10793 Canceled Timer's TimerTaskImpl not removed from ScheduledExecutorService thread pool
- Resolved
- relates to
-
EJBTHREE-1330 EJB timer service should use a thread pool to avoid OOM
- Resolved