Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 18 Feb 2011 17:37:38 +0000 (UTC)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <189123187.1377.1298050658461.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Closed: (DERBY-4067)
 ClientConnectionPoolDataSource.getPooledConnection and
 ClientXADataSource.getXAConnection ignore connection attributes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristian Waagan closed DERBY-4067.
----------------------------------


Closing, assuming all work has been done for this issue now.

> 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