Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Date: Wed, 07 Nov 2007 16:07:06 +0100
From: Knut Anders Hatlen <Knut.Hatlen@Sun.COM>
Subject: Re: Distributed Protocol Error
In-reply-to: <20071107124946.GD14536@khepri35.norway.sun.com>
Sender: Knut.Hatlen@Sun.COM
To: Derby Discussion <derby-user@db.apache.org>
Message-id: <wjo8y7da2ixx.fsf@khepri41.norway.sun.com>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <20071107115437.GC14536@khepri35.norway.sun.com>
 <D22C3DAACAC1364C839C21082B57B62001BEB2C7@mail05.curamsoftware.com>
 <20071107124946.GD14536@khepri35.norway.sun.com>
User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (usg-unix-v)

"Bernt M. Johnsen" <Bernt.Johnsen@Sun.COM> writes:

>>>>>>>>>>>>> Suman N wrote (2007-11-07 12:01:16):
>> Hi,
>> 
>> Thanks for the reply. Now I know why I get this error. But what needs to
>> be done to eliminate it.(i.e How can I make my application to talk the
>> Derby client protocol (DRDA) and how can I make the server to run with
>> SSL encryption enabled?).
>
> By default, neither the client, nor the server will run with SSL
> encryption enabled. DRDA is the Derby client protocol, and will
> allways be used in Derby client server communications. My point was
> that if some application which was not a Derby client (or other DRDA
> client, which is possible since DRDA is an open standard and also used
> by e.g. DB2 clients) tried to connect to a Derby server, you would get
> that error message.

A more likely explanation is that you have come across a bug in
Derby. If you could post the steps needed to reproduce the error,
someone might come up with a workaround or a fix.

-- 
Knut Anders