OC4J 10.1.3: EJB3 - How to catch SQLExceptions in a SessionBean

Question

Hi,
originally I posted this a few minutes ago in the toplink forum, but I'm
unsure if this better suits here. So exceptionally, I post it here as well with a
reference to:
EJB3 - How to catch SQLExceptions from within a stateful session bean
I would like to catch any exception while persisisting the data right in my stateful
session bean and don't have to wait until the client receives an SQLException
wrapped in a bunch of other exceptions.
Here some code fragments to illustrate my problem:
// in Client:
InitialContext ctx = new InitialContext();
statefulWork =  (StatefulWork) ctx.lookup("StatefulWork");
try {
  statefulWork.doIt();
} catch (Throwable t) {
  // don't want to implement db-failover here, even though this works
// in SSB
@Resource
private EntityManager em;
public void doIt() {
        try {
            // create some entites here, do some loops, long running transaction
            em.persist(oneOfMyEntityObjects);
            // set some state in the SSB here
        } catch (Throwable t) {
            // I want to catch all exceptions the persistence provider (toplink) gets
            // but I don't get any here :-(
            // this should be to implement proper retry after reconnect (RAC with TAF)
}In my testcase I issue a shutdown abort while insert statements are executed.
The client receives an EJBException, but within the SSB nothing...
How to change this behavior?
Here is what one can find in the OC4J log:
[TopLink Warnung]: 2006.03.27 03:25:32.220--UnitOfWork(13386)--Thread(Thread[RMICallHandler-0,5,RequestThreadGroup])--Exception [TOPLINK-4002] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.exceptions.DatabaseException
Interne Exception: java.sql.SQLException: ORA-25402: transaction must roll back
Fehlercode:25402
Call:INSERT INTO T_RUN_DETAILS (ID, INS_TIME, COUNTER, RUN_ID) VALUES (105781, '2006.03.27 03:23:55', 450, 801)After that the transaction is properly rolled back (automatically) and the client
could implement the failover code, but I could not find a possibility to control this
at server side. Even with BMT I could not manage to catch this exception. I
wouldn't have a problem if I had to call ctx.setRollbackOnly() myself.
Hope someone can help. I'm getting a little desperate here.
Thanks,
Eric

Answer 1

Thanks to the help of James Sutherland I managed to get this working.
I had to add a call to em.flush() and use BMT for the SSB. For details please follow my link to the toplink-forum!
James thinks OC4J can handle automatic transaction retries but wasn't sure about how to configure this in OC4J. Anyone can help?
Regards,
Eric