There are indications that the jdk5 implementation of javax.management.timer.Timer uses internally a single-threaded implementation for executing scheduled tasks, so scheduling of multiple tasks is affected when moving from jdk1.4 and the jboss implementation of Timer, to a jdk5 runtime.

The JBossMX Timer implementation in contrast uses a dynamically extensible thread pool to execute scheduled tasks. Since we don't control the jdk5 implementation, a simple solution is to clone the jboss timer into a new package, e.g. org.jboss.javax.management.timer.Timer, for those that want to stick with the jboss implementation.