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] Updated: (GERONIMO-4350) Connection proxying to imitate DissociatableManagedConnection can easily cause problems
Date Fri, 29 May 2009 02:14:45 GMT

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

David Jencks updated GERONIMO-4350:
-----------------------------------

    Fix Version/s:     (was: 2.2)
                   Wish List

unlikely to get resolved any time soon.

> Connection proxying to imitate DissociatableManagedConnection can easily cause problems
> ---------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4350
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4350
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: connector
>    Affects Versions: 2.1, 2.1.4, 2.2
>            Reporter: David Jencks
>            Assignee: Dain Sundstrom
>             Fix For: Wish List
>
>
> We have some code to imitate the DissociatableManagedConnection to avoid connection leaks
that proxies connections from the supplied ManagedConnectionFactory: the proxy implements
all the interfaces of the connection, but not the class itself.  However, there's nothing
stopping the ConnectionFactory from casting the (now proxied) connection to the implementation
class it expects.
> The TxConnect project at sourceforge illustrates this approach in the EisConnectionFactory.
> http://txconnect.sourceforge.net
> One possible solution would be to have a flag to turn on this proxying behavior.  I don't
immediately see a way to detect if the problem will occur.

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


Mime
View raw message