Hi, that solves the deadlock and exception problems, but when I remove that line from my configuration, I still have that rollback issue, that is OpenJPA sends the delete statements to the database but issues a rollback only, no commit (see my example project with the "ROLLBACK_persistence.xml" configuration where the BrokerImpl property is commented out)
Do you have any idea why this is so? Regards, Mike -----Ursprüngliche Nachricht----- Von: Pinaki Poddar [mailto:[email protected]] Gesendet: Montag, 13. Juni 2011 22:35 An: [email protected] Betreff: Re: concurrent thread exception plus deadlock on delete statement using slice Hi, Slice uses its own Broker (DistributedBrokerImpl) implementaion. Whereas your configuration tries to overwrite that with <property name="openjpa.BrokerImpl" value="non-finalizing"></property> For a quick turnaround, I would advise that you remove that from your configuration. If the problem persists still, I will examine it further. I will add this caveat/limitation in our documentation. Regards -- ----- Pinaki -- View this message in context: http://openjpa.208410.n2.nabble.com/concurrent-thread-exception-plus-deadlock-on-delete-statement-using-slice-tp6449143p6471718.html Sent from the OpenJPA Users mailing list archive at Nabble.com. ___________________________________________________ SMA Solar Technology AG Aufsichtsrat: Guenther Cramer (Vorsitzender) Vorstand: Juergen Dolle, Roland Grebe, Uwe Hertel, Pierre-Pascal Urbon, Marko Werner Handelsregister: Amtsgericht Kassel HRB 3972 Sitz der Gesellschaft: 34266 Niestetal USt-ID-Nr. DE 113 08 59 54 WEEE-Reg.-Nr. DE 95881150 ___________________________________________________
