Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <446F3232.2070006@amberpoint.com>
Date: Sat, 20 May 2006 08:13:54 -0700
From: Bryan Pendleton <bpendleton@amberpoint.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: NSinSameVM can't find DRDAProtocolExceptionInfo class
 (solarisx86,
 JDK 1.4)
References: <446E3CE9.2060007@sun.com> <x1oxves1pihe.fsf@sun.com>
 <x1oxmzddpgc7.fsf@sun.com>
In-Reply-To: <x1oxmzddpgc7.fsf@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

>> I think this is a problem with the test and/or the server code.
>> Apperently there is a race condition between the connection being
>> closed and the shutdown of the server.  This test starts its own
>> server and then opens and closes a connection to it, in this case via
>> the derby client driver.  Skeleton code:

This is very interesting! I don't know what is going on here, either, but
it sounds very similar to the issues that I've been investigating with
Deepa and Kathey under DERBY-1326 and DERBY-1219.

I'm hoping to put some effort into Network Server session/connection
management in the context of DERBY-1326.

I think it is too soon to tell whether the problems you are seeing
are identical to those of DERBY-1326 and DERBY-1219, but I certainly
think that this part of the system will benefit from having a number
of contributors carefully analyzing it.

thanks,

bryan