Hi, Can you please share the complete stack trace? Perhaps, sharing a small GitHub example replicating the scenario can be useful to navigate your issue. Is the jtaManaged false intended? It may be related with a DB deadlock and the statement was rolled back causing the timeout in the distributed transaction.
El mar., 26 mar. 2019 a las 2:02, zsaade (<[email protected]>) escribió: > Dear All > > I have an EAR file that i'm deploying under > <apache-tomee-plume-7.1.0-home>\apps folder, I added the the below > Datasource configuration in the tomee.xml file located under > <tomee-home>\conf: > > <?xml version="1.0" encoding="UTF-8"?> > <tomee> > <Deployments dir="apps" /> > <Resource id="services" type="javax.sql.DataSource"> > [jdbc-driver] > [jdbc-url] > userName test_server > password test_server > jtaManaged false > defaultAutoCommit true > </Resource> > </tomee> > > In my EJB method when i'm doing any Database update I'm facing database > lock > on the updated tables, the lock is not release until I shutdown tomee, > Kindly advice if there's still missing configurations at the level of the > Datasource configuration or in the EJB methods? > > Exception: timeout: distributed transaction waiting for lock > > Thanks & Best Regards > > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html > -- Atentamente: César Hernández.
