Hi Sargol, I don't think there is an OpenJPA property which would help you here. If you want to lower the isolation level, try doing it on the datasource configuration or wherever you configure the distributed transaction instead of setting the openjpa.jdbc.TransactionIsolation property.
I would recommend that you first figure out the sequence of SQL statements that leads to the lock timeout error. It is a tedious job but without it you risk looking blindly for the solution. Cheers, Milosz > > Hi, > For your information, we got the "ORA-02049: timeout: distributed > transaction waiting for lock" error when the .net side of application had > not been > involved in the transaction. Does it show that the problem is not related to > the distributed transaction configurations? Is there any special property > that we > must have configured regarding Openjpa locking. > > Thank you in advance. > > Regards, > Sargol >
