You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2007/03/22 02:55:32 UTC
[jira] Closed: (OPENEJB-540) Rolling back a transaction in which a
Timer is cancelled results in a non-functional timer
[ https://issues.apache.org/jira/browse/OPENEJB-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Miller closed OPENEJB-540.
--------------------------------
Resolution: Fixed
On cancel(), timer's are removed from the TimerStore. This behavior is per-spec. If the transaction is cancelled, we now add the timer back into the TimerStore.
> Rolling back a transaction in which a Timer is cancelled results in a non-functional timer
> -------------------------------------------------------------------------------------------
>
> Key: OPENEJB-540
> URL: https://issues.apache.org/jira/browse/OPENEJB-540
> Project: OpenEJB
> Issue Type: Bug
> Affects Versions: 3.0
> Reporter: Kevan Miller
> Assigned To: Kevan Miller
> Fix For: 3.0
>
>
> If a Timer is cancelled, but the Transaction is rolled back, the Timer will never fire.
> When the Timer is cancelled, the corresponding TimerData is removed from the TimerStore. However, the TimerData is never added back to the TimerStore in the event of a Rollback.
> Most appropriate fix seems to be add the TimerData back to the TimerStore during Rollback processing...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: [jira] Closed: (OPENEJB-540) Rolling back a transaction in which a Timer is
Posted by khurram hanif <kh...@hotmail.com>.
Please remove me from Mailing List, Thanks in advance !!!
M Khurram
The only way to contorl or finish successfully "Think before it will happen,
as when it will be happening you will not have time to Think"
>From: "Kevan Miller (JIRA)" <ji...@apache.org>
>Reply-To: openejb-dev@incubator.apache.org
>To: openejb-commits@incubator.apache.org
>Subject: [jira] Closed: (OPENEJB-540) Rolling back a transaction in which a
>Timer is cancelled results in a non-functional timer
>Date: Wed, 21 Mar 2007 18:55:32 -0700 (PDT)
>
>
> [
>https://issues.apache.org/jira/browse/OPENEJB-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>]
>
>Kevan Miller closed OPENEJB-540.
>--------------------------------
>
> Resolution: Fixed
>
>On cancel(), timer's are removed from the TimerStore. This behavior is
>per-spec. If the transaction is cancelled, we now add the timer back into
>the TimerStore.
>
> > Rolling back a transaction in which a Timer is cancelled results in a
>non-functional timer
> >
>-------------------------------------------------------------------------------------------
> >
> > Key: OPENEJB-540
> > URL: https://issues.apache.org/jira/browse/OPENEJB-540
> > Project: OpenEJB
> > Issue Type: Bug
> > Affects Versions: 3.0
> > Reporter: Kevan Miller
> > Assigned To: Kevan Miller
> > Fix For: 3.0
> >
> >
> > If a Timer is cancelled, but the Transaction is rolled back, the Timer
>will never fire.
> > When the Timer is cancelled, the corresponding TimerData is removed from
>the TimerStore. However, the TimerData is never added back to the
>TimerStore in the event of a Rollback.
> > Most appropriate fix seems to be add the TimerData back to the
>TimerStore during Rollback processing...
>
>--
>This message is automatically generated by JIRA.
>-
>You can reply to this email to add a comment to the issue online.
>
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.com/