Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 14 Feb 2011 17:37:57 +0000 (UTC)
From: "Lily Wei (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <657960270.15234.1297705077498.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2135492980.11197.1297450137600.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (DERBY-5028) InterruptResilienceTest passes with
 IBM 1.6 SR9 but creates javacore dumps
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994375#comment-12994375 ] 

Lily Wei commented on DERBY-5028:
---------------------------------

There are two way to avoid the problem: deleting them to the cleanup or set the derby.stream.error.extendedDiagSeverityLevel higher so javacore file does not get created.

> InterruptResilienceTest passes with IBM 1.6 SR9 but creates javacore dumps 
> ---------------------------------------------------------------------------
>
>                 Key: DERBY-5028
>                 URL: https://issues.apache.org/jira/browse/DERBY-5028
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.8.0.0
>         Environment: windows xp, IBM java 1.6 SR9
>            Reporter: Myrna van Lunteren
>             Fix For: 10.8.0.0
>
>         Attachments: DERBY-4463_ibm15skiponly.diff
>
>
> After DERBY-4463, it was found there was a bug with the IBM jvms in the handling of interrupt() and waitFor().
> This is fixed with IBM 1.6 SR9 (and is planned for IBM 1.5 SR13).
> As SR9 is now GA, I thought to adjust the skipping of this test to only with ibm 1.5.
> However, I now notice that the test drops java core dumps with ibm 1.6 SR6. It does not do this with Sun's 1.6 jvm.
> I also believe that it didn't do this a couple of weeks ago when I first tried this with ibm 1.6 SR9, so I think something has changed in derby, but it is possible I was not paying proper attention.

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