Atomikos Forum

We are using Atomikos on top of Oracle JDBC. Our web app runs on Tomcat 6. Every night, the database is update with new stored procedures at which time the DBA kills all open sessions from Tomcat to Oracle.

After this operation, the first call to a stored procedure results in: raised -3: the XA resource detected an internal error

JDBC logging reveals that this due to the following error in OJDBC:
ORA-00028: your session has been killed

Is there a way Atomikos can gracefully recover from this without actually raising an exception all the way back to the caller? I was thinking along the lines of establishing a new session on the fly after having encountered this error?

Any ideas? Possible? Feasible?

Thanks!

Did you try setting a testQuery?

HTH