Description of problem: ejb timer service creates empty directories for all ejbs including those without timers Empty directories are being created for all ejbs, even those that do not use timers. $JBOSS_HOME/.../data/timer-service-data/ Version-Release number of selected component (if applicable): JBoss EAP 6.0.1 How reproducible: Steps to Reproduce: 1. Deploy an ejb jar that does not use timers 2. You will see an empty directory created in $JBOSS_HOME/.../data/timer-service-data/ Actual results: An empty directory is created here: $JBOSS_HOME/.../data/timer-service-data/ Expected results: No directory is created when the EJB does not use a timer Additional info:
Stuart Douglas <stuart.w.douglas> updated the status of jira AS7-6357 to Resolved
Verified in EAP 6.1.1.ER3
Jaikiran, can I request some deeper explanation of how this was rectified and what was causing it? Ideally we need to know what the problem was in the code, how this manifested in the product (in this case, creating empty folders), what was changed to fix it, and how the product behaves now (I assume it no longer creates unnecessary folders). Thanks for any assistance you can offer.
The timer service was being created for every EJB that was eligible to have a timer service, and as a result it would eagerly create a directory to store the timer data when the service started. Now we only start a real timer service for EJB's that have timeout or schedule methods, other EJB's just use a non-functional timer service, that can still be looked up in JNDI as per the Java EE specs, but does not allow you to schedule timers (as the EJB does not have a timeout method).
Thanks for the input Stuart. I've added a release note and marked it for inclusion in the document. Please comment if the text above is inaccurate in any way.