Incorrect transactional semantics

[divine_comedy]

I am wondering if anybody has experienced this before but here it goes.
We are using MDBs to persist error messages to the database. Then the following messages pop up :
13:03:22,620 WARN [LocalTxConnectionManager$LocalConnectionEventListener] prepare called on a local tx. You are not getting the semantics you expect!

This might or might not have to do with the MDBs. I am simply noticing that the JMS setup involves a lot of XA Transaction setup while our database has a LocalTx setup. If this is the cause of that message, can anyone tell me how to use the local Tx Manager for JMS ?

Thanks a whole bunch

[slawsonb]

I get the same warning when using MDBs and PostgresQL. Can this be safely ignored?

[sstephens]

I am getting the same problem. Can someone please eloborate? I know it has to do with the XA Transaction used by jms and the local transactions used by my Datasource. I have also read that XA Datasources are not stable in Jboss as of 3.0.6.

[adrian.brock]

Yes trying to mix local db transactions
with XA JMS gives this warning. The local
db transaction cannot be prepared so the commit
may fail. This is too late for two-phase commit
which is why you get the warning.

3.0.7 includes workarounds for some of the
bugs in the Oracle XA db drivers. In particular
making sure the same connection is always
used in the same transaction.

Regards,
Adrian