[
https://issues.apache.org/jira/browse/GERONIMO-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dain Sundstrom closed GERONIMO-4350.
------------------------------------
Resolution: Invalid
Assignee: David Jencks (was: Dain Sundstrom)
The problem was in user code that was attempting to downcast a connection proxy
to a specific implementation class which is not allowed by the JEE Connector
specification.
> 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.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.1.4, 2.2
>
>
> 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.
