If an ear defines an ejb module that has within it for example a singleton timer bean with a method like so:

@Schedule(hour="*", minute="*") 
public void autoTimer() {}

that has deployed/started/then persisted and changes to

@Schedule(hour="*", minute="*", info="IDecidedToNameMyTimer") 
public void autoTimer() {}

in a subsequent deployment, the timer will not have the 'info' updated in the running timer.

It's not entirely clear to me based on the spec that it should in fact update the 'info', but it's seems like the 'right' thing to do.  I'm uncertain whether it should count as a new auto timer and thus cancel the previously persisted one though, or whether the previously persisted one should update with the new 'info'.  I'm inclined to think the former is more correct.

Note that I believe the issue is in the TimerServiceImpl.restoreTimers method where it is matching currently active and new auto timers, and appears to apply to all wildfly versions.