You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Trejkaz (JIRA)" <de...@db.apache.org> on 2005/10/12 03:00:05 UTC

[jira] Commented: (DERBY-618) Make the client driver connection URL work when spaces are in the URL.

    [ http://issues.apache.org/jira/browse/DERBY-618?page=comments#action_12331853 ] 

Trejkaz commented on DERBY-618:
-------------------------------

I just tried doing this by modifying ClientDriver.java to remove the space separators from all StringTokenizer calls.  If I do that, the connection works, but I get a new error a bit later on:

Caused by: org.apache.derby.client.am.DisconnectException: A communication error has been detected. Communication protocol being used: Reply.fill(). Communication API being used: InputStream.read(). Location wh
ere the error was detected: insufficient data. Communication function detecting the error: *. Protocol specific error codes(s) TCP/IP SOCKETS
        at org.apache.derby.client.net.NetAgent.throwCommunicationsFailure(NetAgent.java:362)
        at org.apache.derby.client.net.Reply.fill(Reply.java:193)
        at org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Reply.java:212)
        at org.apache.derby.client.net.Reply.ensureBLayerDataInBuffer(Reply.java:225)
        at org.apache.derby.client.net.NetStatementReply.parsePKGNAMCSN(NetStatementReply.java:1478)
        at org.apache.derby.client.net.NetStatementReply.parsePKGSNLST(NetStatementReply.java:1721)
        at org.apache.derby.client.net.NetStatementReply.parseRSLSETRM(NetStatementReply.java:1080)
        at org.apache.derby.client.net.NetStatementReply.parseResultSetProcedure(NetStatementReply.java:343)
        at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(NetStatementReply.java:279)
        at org.apache.derby.client.net.NetStatementReply.readExecuteCall(NetStatementReply.java:97)
        at org.apache.derby.client.net.StatementReply.readExecuteCall(StatementReply.java:74)
        at org.apache.derby.client.net.NetStatement.readExecuteCall_(NetStatement.java:174)
        at org.apache.derby.client.am.Statement.readExecuteCall(Statement.java:1105)
        at org.apache.derby.client.am.PreparedStatement.flowExecute(PreparedStatement.java:1426)
        at org.apache.derby.client.am.PreparedStatement.executeQueryX(PreparedStatement.java:299)
        at org.apache.derby.client.am.DatabaseMetaData.executeCatalogQuery(DatabaseMetaData.java:1767)
        at org.apache.derby.client.am.DatabaseMetaData.getTablesX(DatabaseMetaData.java:1148)
        at org.apache.derby.client.am.DatabaseMetaData.getTables(DatabaseMetaData.java:1101)
        at com.nuix.store.database.AbstractDatabase.tableExists(AbstractDatabase.java:189)
        ... 12 more


> Make the client driver connection URL work when spaces are in the URL.
> ----------------------------------------------------------------------
>
>          Key: DERBY-618
>          URL: http://issues.apache.org/jira/browse/DERBY-618
>      Project: Derby
>         Type: Improvement
>   Components: Network Client
>     Versions: 10.1.1.0
>     Reporter: Trejkaz

>
> At present, if I want to connect to a database on a Derby server which has a space in the path, there is no way to do it.
> This can be done with the embedded driver, and for consistency it would be good if it worked for the client driver in the same fashion.

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