-
Task
-
Resolution: Done
-
Major
-
None
-
None
The EJB3 timerservice-mk2.jar is only applicable for EJB3.x beans. So if there are no EJB3.x deployments in the server, then there's no point in deploying that timerservice-mk2.jar. Deploying that jar on-demand (i.e. when the first EJB3.x deployment becomes available) is also going to improve the AS boot time.
The referenced forum thread has more details.