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 (nike.apache.org: local policy)
From: Daniel Noll <daniel@nuix.com>
To: "Derby Discussion" <derby-user@db.apache.org>
Subject: Re: Network protocol error in prepareStatement()
Date: Tue, 13 Nov 2007 10:35:35 +1100
User-Agent: KMail/1.9.7
References: <200711121539.20497.daniel@nuix.com>
 <47388BCA.3010304@amberpoint.com>
In-Reply-To: <47388BCA.3010304@amberpoint.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200711131035.35858.daniel@nuix.com>

On Tuesday 13 November 2007 04:22:18 Bryan Pendleton wrote:
> > I'm getting this unusual exception during prepareStatement():
>
> Hi Daniel,
>
> This could possibly be due to a bug in Derby. Can you reproduce
> the problem? If so, can you gather more information? Here is
> a wiki page which provides guidance about how to proceed with
> gathering more information:
>
> http://wiki.apache.org/db-derby/ProtocolDebuggingTips

It apparently does happen every time, whether from remote hosts or localhost.

This is embedded in an application though so changing the connection 
properties isn't going to be easy, but do you think changing the system 
property derby.drda.debug to true on the server would generate enough output 
to diagnose the problem?

Failing that I might have to step our customer through using a third-party 
database browsing tool to open the database, but those aren't the easiest to 
use and I sort of fear leaving that sort of power in the hands of an end 
user.

Daniel