db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepa Remesh <drem...@gmail.com>
Subject Re: [jira] Commented: (DERBY-374) Invalid URL with Derby Client when connecting to Network Server causes protocol exception.
Date Mon, 03 Oct 2005 23:32:08 GMT
On 10/3/05, Kathey Marsden (JIRA) <derby-dev@db.apache.org> wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-374?page=comments#action_12331190 ]
> Kathey Marsden commented on DERBY-374:
> --------------------------------------
> I was thinking with this change that it would be good to check the problem url using
> 1)  10.1 client with the 10.2 server
> 2) 10.2 client with the 10.1 server.
> Just to make sure it doesn't introduce a hang or anything worse than the protcol error
we were getting before.
> Deepa, would you mind checking that out?

I tried all the Client URLs added in the test jdbcapi/checkDriver.java.

With 10.1 server and 10.2 client : behaviour same as before this
patch. (protocol error)
With 10.2 server and 10.1 client: Instead of protocol error, client
throws a SQLException with null message. ij displays:
ERROR      : DERBY SQL error: SQLCODE: -1, SQLSTATE:      , SQLERRMC: null

This does not look so good. It happens because the server is changed
to return null SQLCARD with RDBAFLRM but the old client does not
interpret this null SQLCARD and just throws it out as SQLException to
the caller.


View raw message