Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4C6D7C9A.6070401@sbcglobal.net>
Date: Thu, 19 Aug 2010 11:48:58 -0700
From: Kathey Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: Replication and weme failures last night in IBM runs
References: <4C6D5A4C.60901@sbcglobal.net>
In-Reply-To: <4C6D5A4C.60901@sbcglobal.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

  On 8/19/2010 9:22 AM, Kathey Marsden wrote:
>
>
> FYI
> I looked at the IBM results this morning and see on ibm 1.6 all the 
> Replication tests failed with trace similar to the one below.
> I did not do a full run after changing the DERBY-2026 tests to reset 
> the loginTimeout to 0, so am doing that now to
> see if somehow there was an impact.  IBM 1.5 was fine.  The Sun 
> tinderbox JDK 1.6 run looks fine.  The Sun nightly run did not run.
>

Replication tests  look  fine on my machine with a full run with:
$ java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr8-20100409_01(SR8))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 
jvmwi3260sr8-201004
01_55940 (JIT enabled, AOT enabled)
J9VM - 20100401_055940
JIT  - r9_20100401_15339
GC   - 20100308_AA)
JCL  - 20100408_01

.....

testReplication_Encrypted_1_miniLoad_negative used 29672 ms .
testReplication_Local_3_p6_autocommit_OK used 53812 ms
Time: 7,735.719

OK (12822 tests)

So I think something specific to the machine or intermittent  must have 
happened last night.

I can reproduce the weme problem and am looking at that now.