db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1586) The attributesAsPassword property doesn't work correctly with EmbeddedConnectionPoolDataSource
Date Wed, 26 Jul 2006 07:35:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1586?page=all ]

Knut Anders Hatlen updated DERBY-1586:

    Attachment: 1586-v1.diff

Attached '1586-v1.diff' to address the problem. EmbeddedConnectionPoolDataSource.createPooledConnection()
took a requestPassword parameter that it didn't pass along to the EmbedPooledConnection it
created. The same bug was also present in EmbeddedConnectionPoolDataSource40. It was fixed
by forwarding the parameter to the constructor of EmbedPooledConnection.

The patch enables DataSourcePropertiesTest in all frameworks (but not for jdk1.3/j2me because
it accesses XADataSource). Derbyall runs cleanly. Reviews would be appreciated. Thanks!

> The attributesAsPassword property doesn't work correctly with EmbeddedConnectionPoolDataSource
> ----------------------------------------------------------------------------------------------
>                 Key: DERBY-1586
>                 URL: http://issues.apache.org/jira/browse/DERBY-1586
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: 1586-test.diff, 1586-v1.diff, 1586-v1.stat
> When attributesAsPassword is true, EmbeddedConnectionPoolDataSource.getPooledConnection()
appends the default password to the connection url. This leads to a malformed url error if
the password is not on the form "xxx=yyy". If the password is on the form "xxx=yyy", it might
cause other unexpected consequences (for instance if it is "shutdown=true"). This is not a
problem with EmbeddedDataSource or EmbeddedXADataSource. In Derby, it works as expected,
so this is a regression.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message