Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 23 Feb 2011 12:34:38 +0000 (UTC)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <963833152.10736.1298464478755.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (DERBY-3624) testfailure in storetests/st_derby715
 with ibm 1.5 on iseries machine; one deadlock message missing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren updated DERBY-3624:
--------------------------------------

    Urgency: Normal
     Labels: derby_triage10_8  (was: )

> testfailure in storetests/st_derby715 with ibm 1.5 on iseries machine; one deadlock message missing
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3624
>                 URL: https://issues.apache.org/jira/browse/DERBY-3624
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.4.1.3
>         Environment: iseries, ibm 1.5.: 
> java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05)
> Classic VM (build 1.5, build JDK-1.5, native threads, jitc_de)
>            Reporter: Myrna van Lunteren
>              Labels: derby_triage10_8
>         Attachments: derby.log, st_derby715.tmp
>
>
> I saw this fail once; a couple of reruns didn't duplicate the problem.
> The only difference appears to be that one of the deadlock messages is missing from the output.
> 4 del
> < Got a Deadlock.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira