There is nothing in TimerTasks to make them cluster aware, so it schedules a new task for each JVM. You could implement this yourself, by having them check whether another is already running (via some locking mechanism such as a process available over RMI). Or if your clustered environment is an
ejb container you could use an EJB Timer service.
[ May 21, 2008: Message edited by: Paul Sturrock ]