Hi All,
I'm using Java 5, JBoss 4.0.2, Oracle 9i and the
GeneralPurposeDatabasePersistencePlugin for EJB Timer persistence. I have
changed the JBoss type mapping (in standardjbosscmp-jdbc.xml) for a BLOB to a
RAW(2000) because Oracle BLOBs don't work with generic JDBC code.
Creating timers works fine and the timers execute as expected, calling the
appropriate ejbTimeout method. Timer rows appear in the TIMERS table. After a
server shutdown and restart, timers are restored with correct data, including
the INFO column, which is a RAW(2000) as mentioned above.
The issue seems to be that, if I cancel a timer from within a Required
transaction EJB method, the timer remains in the DB. I can see that the
Timer's status was set to CANCEL in the DEBUG statements in the JBoss log.
When the server is gracefully shutdown and restarted, the cancelled timer is
restored as active.
Is this intentional/expected behavior? I was expecting that cancel() would
remove a persistent Timer. Has anyone else had this issue?
I have tried searching the forums and read the following threads:
Phantom timeout
Ejb timers and persistence reactivation
They are closely related, but not exactly.
TIA,
Vick Fisher
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918526#3918526
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3918526
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
