Yes, we try to create the timers on startup. This is done in a startup
servlet which looks for a timer with the name we want and if it's not there,
it is created. This was the only way in 2.1 that I could find that would
create the timer only once in the cluster. EJB 3.1 may provide a better
way, I haven't researched it yet.
Anyway my point was to rule out the timers as the source of my deployment
problems, so this code is temporarily disabled.
--
[Message sent by forum member 'culli']
View Post: http://forums.java.net/node/789009