This content has been marked as final.
Show 5 replies
-
1. Re: TwoPhaseCoordinator.afterCompletion - failed for com.arj
marklittle Jan 15, 2007 7:02 AM (in response to lgsw_sam)Which version of JBossTS?
-
2. Re: TwoPhaseCoordinator.afterCompletion - failed for com.arj
lgsw_sam Jan 15, 2007 7:57 AM (in response to lgsw_sam)We are using 4.2.2 version of JBossTS
-
3. Re: TwoPhaseCoordinator.afterCompletion - failed for com.arj
marklittle Jan 15, 2007 8:17 AM (in response to lgsw_sam)Unfortunately the exception just says that something went wrong in an afterCompletion call. We'll improve the output in the next release, but that won't help you now. Can you attach a debugger?
All afterCompletion's are courtesy calls anyway, so whatever the implementation is shouldn't be relying on it being called. This should have no affect on the consistency of your data; it certainly can't affect the outcome of the transaction.
But a failure is a failure and it would be nice to know what is causing it. -
4. Re: TwoPhaseCoordinator.afterCompletion - failed for com.arj
lgsw_sam Jan 15, 2007 9:23 AM (in response to lgsw_sam)Hi Mark!
It seems to be related to one of these persistence.xml properties as when these are removed there's no more of those WARN messages.<property name="hibernate.connection.release_mode" value="after_statement"/> <property name="hibernate.transaction.auto_close_session" value="true"/>
It would indeed be nice to know what's causing that WARN but now we are having different problems and are focusing on them so we don't intend to debug this anymore as we can work around it.
Thanks for your reply's!
Br,
Sami -
5. Re: TwoPhaseCoordinator.afterCompletion - failed for com.arj
marklittle Jan 15, 2007 1:02 PM (in response to lgsw_sam)Glad to have been of assistance.