Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <2419956.1185378871778.JavaMail.jira@brutus>
Date: Wed, 25 Jul 2007 08:54:31 -0700 (PDT)
From: "Prasad Kashyap (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-250) Connector tries to commit after
 connection error
In-Reply-To: <835059964.1087954227606.JavaMail.apache@nagoya>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GERONIMO-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasad Kashyap updated GERONIMO-250:
------------------------------------

    Fix Version/s:     (was: 2.0-M5)
                   Verification Required

> Connector tries to commit after connection error
> ------------------------------------------------
>
>                 Key: GERONIMO-250
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-250
>             Project: Geronimo
>          Issue Type: Bug
>          Components: connector
>    Affects Versions: 1.0-M2
>            Reporter: Simon Godik
>            Assignee: David Jencks
>             Fix For: Verification Required
>
>
> If a resource adapter indicates a connection has had a fatal error, then the connection manager destroys the managed connection but still attempts to commit/rollback at transaction end. This is bad as the connection has already been destroyed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.