Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <42565DCE.3080201@sbcglobal.net>
Date: Fri, 08 Apr 2005 03:32:46 -0700
From: Kathey Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: Derby-128
References: <425629BD.5050906@sun.com>
In-Reply-To: <425629BD.5050906@sun.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Amit Handa wrote:

> Hi,
>
> I tried re producing Derby 128 on Linux but with no success :(
> For me the test NSinSameJVM just seems to pass.
> Is this always re producible or have I missed something here ?
>
> It would be great if any body can throw more light on this ?
>
> thanks,
> Amit
>
>

Hi Amit,

Thanks for looking at this!     To reproduce the problem on Linux, I
think all  you have to do is try to create a database in the root
directory or other unwritable file system via network server.  I say, I
think, because I don't actually have a linux system.  The original bug
(Derby-128)  was discovered by linux users after my  errant checkin to
NSinSameJVM which made it try to create a database in the root directory.

If just trying to create a database in the root directory with network
server does not seem to work as I suspect, or you would like to
reproduce using NSinSameJVM,  you can just temporarily change this line.

82c82
<         String url = jdbcUrlPrefix + databaseFileName;
---
>         String url = jdbcUrlPrefix + "/" + databaseFileName;

or
 svn update -r 125447 NSinSameJVM.java
to get the buggy test before fixed.
Then run on Linux and you should see the NPE.

Let me if that doesn't work.

Kathey