[jboss-jira] [JBoss JIRA] (WFLY-28) ejb timer service creates empty directories for all ejbs including those without timers

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797807#comment-12797807 ] 

RH Bugzilla Integration commented on WFLY-28:
---------------------------------------------

Stuart Douglas <sdouglas at redhat.com> made a comment on [bug 910193|https://bugzilla.redhat.com/show_bug.cgi?id=910193]

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).
                
> ejb timer service creates empty directories for all ejbs including those without timers
> ---------------------------------------------------------------------------------------
>
>                 Key: WFLY-28
>                 URL: https://issues.jboss.org/browse/WFLY-28
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>            Reporter: Brad Maxwell
>            Assignee: Stuart Douglas
>            Priority: Minor
>              Labels: directory, ejb, timer
>             Fix For: 8.0.0.Alpha1
>
>
> ejb timer service creates empty directories for all ejbs include those without timers
> Empty directories are being created for all ejbs, even those that do not use timers.
> $JBOSS_HOME/.../data/timer-service-data/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira