Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 31705 invoked from network); 20 Sep 2005 16:35:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Sep 2005 16:35:45 -0000 Received: (qmail 71102 invoked by uid 500); 20 Sep 2005 16:35:44 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 71067 invoked by uid 500); 20 Sep 2005 16:35:44 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 71056 invoked by uid 99); 20 Sep 2005 16:35:43 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Sep 2005 09:35:43 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,DNS_FROM_RFC_WHOIS,SPF_HELO_FAIL X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.182.146] (HELO e6.ny.us.ibm.com) (32.97.182.146) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Sep 2005 09:35:52 -0700 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e6.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j8KGZU2N021868 for ; Tue, 20 Sep 2005 12:35:30 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay04.pok.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j8KGZUwa051550 for ; Tue, 20 Sep 2005 12:35:30 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id j8KGZTvJ005940 for ; Tue, 20 Sep 2005 12:35:29 -0400 Received: from [127.0.0.1] (sig-9-48-119-3.mts.ibm.com [9.48.119.3]) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j8KGZRHm005721 for ; Tue, 20 Sep 2005 12:35:29 -0400 Message-ID: <43303A4D.9050906@sbcglobal.net> Date: Tue, 20 Sep 2005 09:35:25 -0700 From: Kathey Marsden User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Development Subject: Re: [jira] Updated: (DERBY-374) Invalid URL with Derby Client when connecting to Network Server causes protocol exception. References: <468024357.1127142629464.JavaMail.jira@ajax.apache.org> <432EF50E.7070008@sbcglobal.net> <432F129D.7070400@sbcglobal.net> <58ed70f505092009143e77b951@mail.gmail.com> In-Reply-To: <58ed70f505092009143e77b951@mail.gmail.com> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Deepa Remesh wrote: >I am using RDBAFLRM for failure to find a suitable driver. Is this >okay or is there any specific message type that must be used in such a >case? > > > 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. Kathey