Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <206332717.1121783206579.JavaMail.jira@ajax.apache.org>
Date: Tue, 19 Jul 2005 16:26:46 +0200 (CEST)
From: "Philip Wilder (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-409) ClientDataSource
 setConnectionAttributes("create=true") fails with   "An attempt was made to
 access a database, mydbcreate=true, which was not found."
In-Reply-To: <976563501.1120080358805.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-409?page=all ]
     
Philip Wilder resolved DERBY-409:
---------------------------------

    Fix Version: 10.1.1.0
                 10.1.1.1
                 10.2.0.0
     Resolution: Fixed

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

> ClientDataSource setConnectionAttributes("create=true") fails with   "An attempt was made to access a database, mydbcreate=true, which was not found."
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-409
>          URL: http://issues.apache.org/jira/browse/DERBY-409
>      Project: Derby
>         Type: Bug
>     Versions: 10.1.1.0, 10.2.0.0
>     Reporter: Kathey Marsden
>     Assignee: Philip Wilder
>      Fix For: 10.1.1.0, 10.1.1.1, 10.2.0.0
>  Attachments: ConnectionAttributes.java, Derby409.patch
>
> 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)
> $

-- 
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