ClientDataSource setConnectionAttributes("create=true") fails with "An attempt was made to access a database, mydbcreate=true, which was not found."

• Key: DERBY-409
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Philip Wilder
• Reporter: Kathey Marsden
• Component/s: JDBC
• Affects Version/s: 10.1.1.0, 10.2.1.6
• Fix Version/s: 10.1.2.1, 10.2.1.6

Description

ClientDataSource setConnectionAttributes("create=true") fails with "An attempt was made to access a database, mydbcreate=true, which was not found." The method does not seem to insert a semicolon before the attributes.


run attached repro to produce the error below

$java ConnectionAttributes
embedded setConnectionAttributes
client setConnectionAttributes
org.apache.derby.client.am.DisconnectException: The application server rejected establishment of the connection. An attempt was made to access a database, mydbcreate=true, which was not found.
        at org.apache.derby.client.net.NetConnectionReply.parseRDBNFNRM(NetConnectionReply.java)
        at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(NetConnectionReply.java)
        at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(NetConnectionReply.java)
        at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(NetConnectionReply.java)
        at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(NetConnection.java)
        at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java)
        at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(NetConnection.java)
        at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java)
        at org.apache.derby.client.net.NetConnection.initialize(NetConnection.java)
        at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java)
        at org.apache.derby.jdbc.ClientDataSource.getConnection(ClientDataSource.java)
        at org.apache.derby.jdbc.ClientDataSource.getConnection(ClientDataSource.java)
        at ConnectionAttributes.main(ConnectionAttributes.java:28)
$

Comments

repro

[Kathey Marsden]

This issue would appear to be in
java/client/org/apache/derby/client/am/Connection.java
 databaseName_ = dataSource.getDatabaseName() + attrString;

If there is an attrString, there should be a ";" before it.

[Philip Wilder]

Please see DERBY-406 for an update on the status of this issue.

[Philip Wilder]

This is a potential patch for the issue brought up in DERBY-406
connectionAttributes will now default to null (aka no default)

It had a clean run of derbyall with the exception of the DERBY-273 issue.

[Daniel John Debrunner]

Committed revision 219256.
Excluded file testSecMec.java as it was only a change in spaces.

Philip, it's just a little easier in the future if patch files are from the root of the tree, not a sub-directory.
This allows committers to applie patches consistently, without having to figure out where the root is.

Thanks for the patch.,

[Philip Wilder]

With the latest patch I believe this issue can be considered resolved. The related Derby-406 and Derby-410 issues remain open.

[Andrew McIntyre]

Setting Fix in to 10.2.0.0 only, as the fix has only gone into the trunk.

[Satheesh Bandaram]

Merged this fix into 10.1 branch with change number: 209498

[Kathey Marsden]

reopening to fix fix version

[Deepa Remesh]

reopening to fix fix version

[Rick Hillegas]

Assigning to JDBC component.