Hello, Have you considered using Aries Transaction Control to manage your transactions? This is a much more reliable way to deal with transactions that run across module boundaries, and it is much clearer which resources have “opted in” to the transaction.
Best Regards, Tim On 1 Jun 2018, at 06:39, Mohideen, Kaja (Nokia - IN/Chennai) <kaja.mohid...@nokia.com<mailto:kaja.mohid...@nokia.com>> wrote: Hi, I’m using Aries JPA (in Apache Karaf) for my application where different services (bundles) have their own PersistenceContexts and they use a single Datasource (XA) – everything works fine. All my modules are connecting to a single Datasource, so I have switched to Non-XA DS; now the Transactions seems to be per module (EM) and they are not atomic across modules. I understand that XA would have co-ordinated this earlier. But, is it possible to make them use a Single DS Connection/Transaction to achieve the same effect (like mark PersistenceUnits “extended” or some other technique). I have searched the Aries-JPA repo for mention of PersistenceContextType and found nothing ☹. So, not sure whether Aries JPA supports this and if so – how? Any help is greatly appreciated. // Kaja
