[jira] [Assigned] (GERONIMO-4350) Connection proxying to imitate DissociatableManagedConnection can easily cause problems

["Dain Sundstrom (JIRA)" <ji...@apache.org>]

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

Dain Sundstrom reassigned GERONIMO-4350:
----------------------------------------

    Assignee:     (was: Dain Sundstrom)

> 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
>             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 was sent by Atlassian JIRA
(v6.4.14#64029)