Scheduled timer not deleted on undeploy/redeploy

[enpasos]

jboss 6.1.0-SNAPSHOT (#553):

I deploy an application consisting of only a scheduled task:

@Singleton

public class ScheduleTestBean {

    @Schedule(dayOfMonth = "*", month = "*", year = "*", hour = "*", minute="*", second="*/10")

    public void process() {

                log.info("ScheduleTestBean: " + new Date());

    }

    private static final Logger log = Logger.getLogger(ScheduleTestBean.class.getName());

}

After deploying the scheduled task (ScheduleOn) it logs a message every 10 seconds. After undeploying the application the logging stops. If I comment the "@Schedule" in the code (ScheduleOff) and deploy the application again under the same name the logging goes unexpectedly on.

My current workaround: Never deploy/redeploy an application under the same name again, instead deploy it under a "versioned name".

I am searching for: a better workaround or bug fix.

[jaikiran]

It's a bug actually https://issues.jboss.org/browse/EJBTHREE-2229. I just haven't found the time to fix. I'll see if I can spare some time this/next weekend for this. In the meantime try the workaround (about persistent=false attribute) mentioned in that JIRA (and the referenced threads).

[enpasos]

Thank you. Bug fix sounds great.

Your workaround (persistent=false) helps me for now. I just tested it and to my surprise it even survived a server restart.

[jaikiran]

Matthias Unverzagt wrote:

I just tested it and to my surprise it even survived a server restart.

It just appears to have survived a server restart since the @Schedule is meant to create the timers automatically during the application deployment (which happens during server restart).

[enpasos]

Thank you. The AS behaves as required by the spec :-)

JavaEE6 Spec, 18.2.3 Non-persistent Timers: "For automatic non-persistent timers, the container creates a new non-persistent timer during application initialization for each JVM across which the container is distributed."