Incorrect nextTimeout() and timeRemaining() values for ejb timer in clustered Weblogic
We are experiencing absurd values returned
We are using WebLogic AS 10.3.5 in a clustered environment on Win Server 2008 R2. The Oracle RDBMS is on separate servers in RAC configuration.
Our JEE applications make use of a set of timers, which have been coded and configured for a cluster environment as specified in WebLogic documentation. Timers are persisted in WEBLOGIC_TIMERS and ACTIVE tables in DB.
</code><code>
by getNextTimeout() and getTimeRemainig() on a javax.ejb.Timer
instance. Next timeout is equal to the very moment the timer is started,
and remaining time is equal to 24 hours. Of course, being the next
timeout in the past, the timers never trigger.We are using WebLogic AS 10.3.5 in a clustered environment on Win Server 2008 R2. The Oracle RDBMS is on separate servers in RAC configuration.
Our JEE applications make use of a set of timers, which have been coded and configured for a cluster environment as specified in WebLogic documentation. Timers are persisted in WEBLOGIC_TIMERS and ACTIVE tables in DB.
0