Oracle Weblogic Server (MOSC)

MOSC Banner

Incorrect nextTimeout() and timeRemaining() values for ejb timer in clustered Weblogic

edited Mar 12, 2012 10:16PM in Oracle Weblogic Server (MOSC) 4 commentsAnswered ✓
We are experiencing absurd values returned</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.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center