|
From: Andy D. <an...@ma...> - 2005-11-01 16:38:22
|
On Saturday 29 October 2005 07:12 am, Juergen Hoeller wrote: > ... > However, it's not clear to me what such a special JotmJtaTransactionManager > would have to do to enforce a resume. There doesn't seem to be a > "forceResume"-style method anywhere in the JOTM API. It might be worthwhile > to check out Jonas's usage of JOTM: The Jonas EJB container essentially has > the same requirement, needing to enforce a resume of a transaction. I would > appreciate any help in finding out how to achieve this. I've received some initial feedback from JOTM and Jonas developers, and they say that for JOTM, you can choose to ignore the RollbackException at the point of "resume" to achieve a forced resume (they said that the RollbackException is recoverable at this point, and the transaction should still properly rollback when it is finished). However, they are aware of a bug in which only the first XA resource is re-enlisted with the transaction at resume (because it is after the first "enlist" operation that the RollbackException is thrown, thus causing their enlist loop to abort). They are planning on patching this soon. - Andy |