Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D660D1055D for ; Mon, 4 Nov 2013 17:47:21 +0000 (UTC) Received: (qmail 81811 invoked by uid 500); 4 Nov 2013 17:47:19 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 81797 invoked by uid 500); 4 Nov 2013 17:47:19 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 81787 invoked by uid 99); 4 Nov 2013 17:47:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Nov 2013 17:47:18 +0000 Date: Mon, 4 Nov 2013 17:47:17 +0000 (UTC) From: "Myrna van Lunteren (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DERBY-6400) harness.NetServer method waitFor() is not reflecting timeout values MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren updated DERBY-6400: -------------------------------------- Summary: harness.NetServer method waitFor() is not reflecting timeout values (was: harness.NetServier method waitFor() is not reflecting timeout values) > harness.NetServer method waitFor() is not reflecting timeout values > ------------------------------------------------------------------- > > Key: DERBY-6400 > URL: https://issues.apache.org/jira/browse/DERBY-6400 > Project: Derby > Issue Type: Improvement > Components: Test > Reporter: Myrna van Lunteren > Priority: Minor > Fix For: 10.10.1.3, 10.11.0.0 > > Attachments: DERBY-6400.diff > > > On a slow machine, derbynetclientmats was seen to fail (with no test pass, nor fail) with the following error: > org.apache.derby.drda.NetworkServerControl start > Attempt to shutdown framework: DerbyNetClient > Server Process did not complete in time. Destroying... > Server Process did not complete in time. Destroying... > Exception in thread "main" java.io.IOException: Interrupted system call > at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:275) > at java.io.BufferedInputStream.read(BufferedInputStream.java:334) > at org.apache.derbyTesting.functionTests.harness.BackgroundStreamSaver.run(BackgroundStreamSaver.java:51) > at java.lang.Thread.run(Thread.java:853) > It seems to me that the problem is here that in functionTests.harness.NetServer the waitFor() method has a hard value of 60 in it. Instead, this value should be configurable. > In functionTests.harness.RunTest the waitFor() method uses > TimedProcess tp = new TimedProcess(pr); > tp.waitFor(timeout*60); > It seems NetServer should also be able to check on the timeout value. -- This message was sent by Atlassian JIRA (v6.1#6144)