"Bernt M. Johnsen" <[EMAIL PROTECTED]> 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

Reply via email to