You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Dave Cameron <da...@lmco.com> on 2006/08/23 01:05:53 UTC
Final Clarification
I wanted to bring some closure to this since I started parallel discussion on
the Geronimo Users Mail List.
This has been identified as a Geronimo Bug. It is believed, but I did not
personally verify, that this bug does not exist in Geronimo 1.1.
What happened is I was using ActiveMQ and another XAResource with
GeronimoTransactionManager. This bug occurs when a participating XAResource
throws an XAException during the prepare phase of the commit process. The
transaction cleanup process actually threw the exception I discovered.
ActiveMQ was behaving exactly as it should have in this scenario. It was
GeronimoTransactionManager that did not have as required.
To resolve this I finally patched and built my own
GeronimoTransactionManager since waiting for a new Jencks/ActiveMQ build
compatible with the latest Geronimo isn't in the cards.
I can help other identify how to accomplish this if needed.
--
View this message in context: http://www.nabble.com/STATUS_NO_TRANSACTION-on-rollback--tf2124313.html#a5935379
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Final Clarification
Posted by Dave Cameron <da...@lmco.com>.
Here is what I did.
I downloaded the Geronimo Source from
http://www.apache.org/dyn/closer.cgi/geronimo/1.0/geronimo-1.0-src.zip.
Went to
geronimo-1.0-src/modules/transaction/src/java/org/apache/geronimo/transaction/context
And edited the file like so(Here is the output from a diff -P):
Index: InheritableTransactionContext.java
307c307,308
< status != Status.STATUS_ROLLING_BACK) {
---
> status != Status.STATUS_ROLLING_BACK &&
> status != Status.STATUS_NO_TRANSACTION) {
--
View this message in context: http://www.nabble.com/STATUS_NO_TRANSACTION-on-rollback--tf2124313.html#a6024069
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Final Clarification
Posted by James Strachan <ja...@gmail.com>.
Grea stuff Dave. I wonder could you provide a patch so we can see what
changes you made?
On 8/23/06, Dave Cameron <da...@lmco.com> wrote:
>
> I wanted to bring some closure to this since I started parallel discussion on
> the Geronimo Users Mail List.
>
> This has been identified as a Geronimo Bug. It is believed, but I did not
> personally verify, that this bug does not exist in Geronimo 1.1.
>
> What happened is I was using ActiveMQ and another XAResource with
> GeronimoTransactionManager. This bug occurs when a participating XAResource
> throws an XAException during the prepare phase of the commit process. The
> transaction cleanup process actually threw the exception I discovered.
>
> ActiveMQ was behaving exactly as it should have in this scenario. It was
> GeronimoTransactionManager that did not have as required.
>
> To resolve this I finally patched and built my own
> GeronimoTransactionManager since waiting for a new Jencks/ActiveMQ build
> compatible with the latest Geronimo isn't in the cards.
>
> I can help other identify how to accomplish this if needed.
>
> --
> View this message in context: http://www.nabble.com/STATUS_NO_TRANSACTION-on-rollback--tf2124313.html#a5935379
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/