Are you able to make all the connections XA?
It seems strange that your database "commit" has not committed the database, I would expect the updates to be visible at that point, maybe ask your DB vendor?
Either way, mixing none-XA and XA like this is dangerous imo.
Thanks for your feedback. Well yes, the fact that the commit isn't visible right away seemed strange to me as well. The database we're talking about is Oracle 10. It is important to know that, instead of creating a new JDBC datasource accessing the rule engine database, then end-user "pulls-in" the rule engine tables of interest via a DB-Link into the external database. I had omitted this detail in order to avoid making a complex description even more complex ;-) So the DB-Link was my first suspect, but I rejected the thought since "latency" issues with DB-Links seemed a bit too far-fetched to me. I decided to follow a different route which I'm going to test next week. I created some kind of internal datasource, which allows the end user to query the rule engine database via the entity manager through native queries. This way, all access to the rule engine data are handled by the transaction manager itself and I reckon this should solve the issue I've been facing. This solution also has the positive side-effect that we're getting rid of the DB-Links which were some kind of crutch.
Thanks again for your feedback....