geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cameron, David A" <david.a.came...@lmco.com>
Subject RE: GeronimoTransactionManager IllegalStateException: Status is STATUS_NO_TRANSACTION
Date Mon, 28 Aug 2006 17:17:26 GMT
I posted an explanation of what I modified to get this working here:
http://www.nabble.com/STATUS_NO_TRANSACTION-on-rollback--tf2124313.html 

-----Original Message-----
From: news [mailto:news@sea.gmane.org] On Behalf Of Joerg Heinicke
Sent: Tuesday, August 22, 2006 2:07 AM
To: user@geronimo.apache.org
Subject: Re: GeronimoTransactionManager IllegalStateException: Status is STATUS_NO_TRANSACTION

Cameron, David A <david.a.cameron@...> writes:

> My gut says to fix it for the scenario and not remove something that 
> may have a purpose.  What I would do is add a check to verify that the 
> TransactionImpl is not in STATUS_NO_TRANSACTION status before trying 
> to roll it back.  It has other, similar checks already.  Just not that 
> one.

Yes, this is something I came across as well.
InheritableTransactionContext.rollbackAndThrow() has a check for STATUS_NO_TRANSACTION for
the rollback() on the TransactionManager, but not for the second rollback() directly on the
Transaction instance.

Jörg


Mime
View raw message