[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: EJB TimerService in a clustered environment

2005-04-07 Thread mka
Hi Cosmin, I was wondering how you even get JBOSS to persist the timer events to a database. My problem is I want to ensure my timer events are valid, and continue to work after the server is restarted. Is this possible? Thanks. View the original post :

[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: EJB TimerService in a clustered environment

2005-04-07 Thread kraftek
Hi Marcus. They say that JBoss persists the timers to a database so that, if the server crashes, they will be restored at the next startup. This is true only if the server crashes, but not for a normal shutdown. My feeling is that they delete all timers that are not related to entity beans

[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: EJB TimerService in a clustered environment

2005-04-07 Thread mka
Yes the second one sounds like the best way, and had started to work in that direction. But tell me, how do you get the startup notification from JBOSS? This is the part I'm totally lost. And thanks for the response by the way. View the original post :

[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: EJB TimerService in a clustered environment

2005-03-21 Thread kraftek
The previous code may result in generating duplicate IDs. Here is the corrected code: | package org.jboss.ejb.txtimer; | | import java.math.BigInteger; | import java.net.InetAddress; | | public class BigIntegerClusteredTimerIdGenerator implements TimerIdGenerator { | private