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).
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.
Matthias Unverzagt wrote:
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).
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."