Thanks for your advice Pinaki - will try it. I guess though that these timeouts will not affect aries-jta's transaction timeout but they will still cause the transaction to fail - right?
Yes, I read on this list that the classloading refactoring wasn't successful. Looking forward to a new attempt. Often the most difficult refactoring is also the most necessary... /Bengt 2011/12/21 Pinaki Poddar <ppod...@apache.org> > Hi Bengt, > One way will be to set timeouts of lock and query in persistence.xml. > > <property name="openjpa.LockTimeout" value="30000"/> > <property name="openjpa.ConnectionFactoryProperties" > value="QueryTimeout=5000"/> > > It is also possible to set these timeouts for individual query (passing > them as query hints) or explicit locking via em.lock(...) API calls. > > PS: I know I have not solved the Auditor classloading in OSGi environment. > Actually a large experiment to do that failed. I will make another attempt > to solve it within a smaller scope. > > > ----- > Pinaki Poddar > Chair, Apache OpenJPA Project > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/How-to-configure-transaction-timeout-tp7092641p7115968.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
