On Wednesday, January 21, 2015 at 2:20:24 AM UTC+1, Noel Grandin wrote: > > > The point is that you should not be spawning a child thread and > waiting for it while you have an open transaction. You should commit > the transaction before spawning the child thread. > This is because while a transaction is open that table is locked. > > Sounds like a use case for Spring's Propagation.NEVER:
* Execute non-transactionally, throw an exception if a transaction exists. I begin to understand what you say and why it's a problem. Now in my case, I need to roll back the outer transaction when the inner one fails. I guess there is no good solution besides two-phase commits ... I mean there is no good solution ;-) Regards, Aaron -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
