Transaction.commit() throws NPE?

Shino · **Posted:** Tue Dec 16, 2003 6:01 pm

Working on a transaction involving 7 different tables.

Before I throw code up since it will require some time...

One of the tables always has an attempt at an insert. This insert will fail sometimes due to a unique constraint error, but I don't care if it does, so I do this...

Code:

         try {
            insert( session, rel );
         }
         catch ( Exception e ) {
            // if unique constraint error, ignore
            // else throw Exception
         }

the insert() method basically wraps session.save(). Nothing happens behind the scenes there.

So before I put the rest of the code, does the session or the transaction track exceptions and fail if there is at least one exception?

Currently, it fails inside the commit() method and I never even see the log entry created by ...

Code:

log.debug("commit");

Any ideas?

dimas · **Posted:** Tue Dec 16, 2003 8:06 pm

I would not try to ignore some exception considering them "safe".

Documentation is prety clear on this point:

Quote:

7.9.4. Exception handling
If the Session throws an exception (including any SQLException), you should immediately rollback the transaction, call Session.close() and discard the Session instance. Certain methods of Session will not leave the session in a consistent state.

gavin · **Posted:** Tue Dec 16, 2003 8:49 pm

As Dimas says, the doco is very explicit on this point. There is No Way that we can ensure consistent state b/w the session and the database when an SQLException occurs.

Shino · **Posted:** Wed Dec 17, 2003 10:08 am

I thought that may be an issue.

OK I will query first to see if the record is there.

If I still have a problem after doing this, I will post again in this topic.

Thanks guys.