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
(ie
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 st
There is a problem with timer ID generation (class
org.jboss.ejb.txtimer.BigIntegerTimerIdGenerator) in a clustered environment.
Everything is fine as long as I use for persistence purposes a database per
server in cluster. But if I use a shared database for the whole cluster (which
I find more
