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] Updated: (DERBY-374) Invalid URL with Derby Client when connecting to Network Server causes protocol exception.
Date Wed, 21 Sep 2005 23:51:05 GMT
Deepa Remesh wrote:

>On 9/20/05, Kathey Marsden <kmarsdenderby@sbcglobal.net> wrote:
>>I think that is the best we can do from the server side as we cannot
>>send a full SQLCARD in this case.
>>I am not sure what message the client reports when this is returned by
>>the server. If it does not seem informative enough, we could always add
>>additional checking to the client to have it made clear and make the
>>message match the embedded driver.  But I think you are right in taking
>>the first step of fixing the NPE in the server and returning RDBAFLRM
>>when the server cannot make a connection.
>I am doing the following. In network server, check if a null
>connection is returned by InternalDriver. If so, throw "new
>SQLException("No suitable driver","08001");" to match behaviour with
>embedded driver. The server will use this SQLException to build
>RDBAFLRM and SQLCARD and send it to client.
>When using embedded driver, this exception gets thrown by
>DriverManager.getConnection method.

Hi Deepa,

That sounds like the correct approach except that we need to localize
the message.
Since this message comes from the server message file instead of the
network server message file,  I think we need to  use  one of the 
org.apache.derby.impl.jdbc.Util.generateCsSQLException   methods.


View raw message