geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-2573) Be even more careful not to try to register a Synchronization with a non-active tx
Date Thu, 16 Nov 2006 21:56:39 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-2573?page=all ]

David Jencks closed GERONIMO-2573.
----------------------------------

    Resolution: Fixed

Fixed in rev 475936.  Logging settings changed to point out to turn on the new tracing in
rev 475937.

> Be even more careful not to try to register a Synchronization with a non-active tx
> ----------------------------------------------------------------------------------
>
>                 Key: GERONIMO-2573
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2573
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: connector
>    Affects Versions: 1.2
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: 1.2
>
>
> Previously we fixed a connection tracking problem when we were trying to close connections
twice when the user closed them in an AfterCompletion synch method.  We have to be even more
careful here not to register another synch during the afterCompletion call.  This occurs when
the connection is also obtained in the afterCompletion call rather than during the tx.
> Not doing this currently results in an ignored exception and the connection not being
returned to the pool.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message