db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
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:45:54 GMT
Deepa Remesh wrote:

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

Actually I think that is not any worse  than the protocol error, so is
ok to leave as is.   Especially considering this
combination would happen on upgrade and at that time you probably have
your urls right.  I think I'd really only be
concerned on this one if we saw a hang.  Maybe others have other opinions.

Kathey




Mime
View raw message