db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4067) ClientConnectionPoolDataSource.getPooledConnection and ClientXADataSource.getXAConnection ignore connection attributes
Date Tue, 13 Jul 2010 10:43:50 GMT

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

Kristian Waagan updated DERBY-4067:

    Attachment: derby-4067-1a-update_attrs.diff

Patch 1a makes the data sources update their state from the contents of the connection attribute
string before creating the connection.
Note that I moved the update of the state before obtaining a log writer, as the log writer
construction is dependent on attributes that can be set in the connection attribute string.
I do plan to backport this fix if possible.

This patch is a partial fix only, there are several unresolved issues remaining. I expect
that these will be addressed as part of DERBY-4719.

Regression tests passed (12830 tests).
Patch ready for review.

> 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:,,
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         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.
You can reply to this email to add a comment to the issue online.

View raw message