Hi Gavin,

is there something wrong with JTA transactions?

I used to call sessionFactory.openSession(), use the session and then close it.

Now you have to call session.beginTransaction() and later to commit or rollback the transaction explicitely, otherways you get a NPE at the following line in SessionImpl.java line 3171:

tm.getTransaction().registerSynchronization( new CacheSynchronization(this) );

Sounds like a transaction has to be active upon connect() beeing called ...

Thanx
Markus

This stuff certainly changed in beta 3 (quite intentionally).

I think you might get an NPE here if you have a TransactionManagerLookup configured in your properties, but there is no JTA transaction active when you connect().

Perhaps I need to do a little check to see that there is a JTA transaction.

Are you running inside an appserver or not?

Yeah, I'm running inside JBoss 3.2.

Only to mention it: I didn't connect() explicitly, I suppose this is done implicitly after opening a session and then doing session.load() or similar things.

For now, I added trans.begin() and tans.commit()/rollback() everywhere and it rocks ...

Thanx

And is there a JTA transaction?

Now or before?

Before I had:

session = sessionFactory.openSession();
session.load(...);
session.close();

Now:

session = sessionFactory.openSession();
trans = session.beginTransaction(); /* this ensures a running transaction */
session.load(...);
trans.commit();
session.close();

NO, I mean a JBoss JTA transaction - not a Hibernate transaction!

No, there is no JTA transaction active around my stuff ...

Yeah, so i think that explains it.

If you unset the net.sf.hibernate.transactionmanager_lookup_class property, the NPE will disappear.

Still, I will make it behave a bit more gracefully.

OK, I had a quick chat with Bill Burke, and we now have no more NPEs in JBoss, I hope. In CVS.

Thanks guys, I'll try it.