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: pass (hermes.apache.org: local policy)
Date: Wed, 04 May 2005 10:59:20 -0700
From: David Van Couvering <David.Vancouvering@Sun.COM>
Subject: Re: [PATCH] Jira-189 ResultSetMetaData.getSchemaName and
 ResultSetMetaData.isWritable donot return correct values
In-reply-to: <42785F42.3030606@gmail.com>
To: Derby Development <derby-dev@db.apache.org>
Message-id: <42790D78.8060403@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
 Gecko/20040113
References: <d9619e4a05040514403c4c6196@mail.gmail.com>
 <42605A8A.4080607@debrunners.com> <d9619e4a0504151751519437ff@mail.gmail.com>
 <d9619e4a050417141428a301a9@mail.gmail.com> <4266988D.7080704@debrunners.com>
 <d9619e4a050422094367faab5c@mail.gmail.com>
 <d9619e4a0504241414391e10cf@mail.gmail.com>
 <d9619e4a050427142870108cc1@mail.gmail.com>
 <d9619e4a05050210567fa26b9f@mail.gmail.com> <4276B6EC.3050609@sun.com>
 <d9619e4a05050314341263a218@mail.gmail.com> <427818A1.7050906@sun.com>
 <42785F42.3030606@gmail.com>

Hi, Sunitha.  I don't know if it was encrypted or not.  The diff I got 
from stress.multi shows an overload problem:

7 del
< ...running last checks via final.sql
7 add
 > ...timed out trying to kill all testers,
 >    skipping last scripts (if any).  NOTE: the
 >    likely cause of the problem killing testers is
 >    probably not enough VM memory OR test cases that
 >    run for very long periods of time (so testers do not
 >    have a chance to notice stop() requests

Just for a sanity check, I ran stress.multi on an idle machine (I wasn't 
doing builds or anything else at the time), and this time it passed.  So 
I think my machine was just overloaded and the test timed out.  I don't 
think it's the same as what you're looking at.

David

Sunitha Kambhampati wrote:

> David Van Couvering wrote:
> 
>>  It built fine and passed all the JDBC api tests, except for 
>> stress.multi, which I think is a problem with my machine and not your 
>> source... 
> 
> 
> Which stress.multi test failed.. was it  the encrypted test run ?  The 
> reason I ask is  I am looking into the  encrypted stress.multi failure  
> (Derby241) and wondering if this failure is similar to that one.   If 
> you still have the testrun output,   can you post some details on it  
> ie   - the derby.log , the database  etc.
> 
> Thanks,
> Sunitha.