db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-4067) ClientConnectionPoolDataSource.getPooledConnection and ClientXADataSource.getXAConnection ignore connection attributes
Date Fri, 18 Feb 2011 16:56:39 GMT

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

Mike Matrigali resolved DERBY-4067.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.6.2.3
                   10.5.3.2
         Assignee: Kristian Waagan  (was: Mike Matrigali)

backported to 10.6 and 10.5.  resolving and resetting to original owner.

> ClientConnectionPoolDataSource.getPooledConnection and ClientXADataSource.getXAConnection
ignore connection attributes
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4067
>                 URL: https://issues.apache.org/jira/browse/DERBY-4067
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.3.3.0, 10.4.2.0, 10.5.1.1
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For: 10.5.3.2, 10.6.2.3, 10.7.1.1
>
>         Attachments: derby-4067-1a-update_attrs.diff
>
>
> The methods CCPDS.getPooledConnection and CXADS.getXAConnection fail to pick up attributes
set with setConnectionAttributes(String).
> The current regression tests fail to detect this, because they obtain a connection using
getConnection(). I'm not sure if this method should be present in a XADataSource at all, but
this problem should be addressed by a separate issue.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message