db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-6400) harness.NetServer method waitFor() is not reflecting timeout values
Date Tue, 12 Nov 2013 21:46:17 GMT

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

Myrna van Lunteren resolved DERBY-6400.
---------------------------------------

    Resolution: Fixed

> 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)

Mime
View raw message