db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-303) derbynet/testconnection.java fails
Date Fri, 20 May 2005 21:32:53 GMT
     [ http://issues.apache.org/jira/browse/DERBY-303?page=all ]

David Van Couvering updated DERBY-303:

    Attachment: DERBY-303.diff

Looking at the very helpful test results from Ole, it appears this bug only occurs on Solaris
I can't reproduce on any platforms I have available.    However, a code inspection shows that
I am missing a call to Process.waitFor() The attached patch adds this call; Oystein, can you

see if this fixes it for you on your Solaris 10 x86 box?

> derbynet/testconnection.java fails
> ----------------------------------
>          Key: DERBY-303
>          URL: http://issues.apache.org/jira/browse/DERBY-303
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions:
>  Environment: Seem to occur on several platforms
>     Reporter: Øystein Grøvlen
>     Assignee: David Van Couvering
>  Attachments: DERBY-303.diff
> When I run the testsuite, derbynet/testconnection.java fails.
> testconnection.tmp contains the following:
> Testing testconnection
> org.apache.derby.drda.NetworkServerControl ping 
> Could not connect to Derby Network Server on host localhost, port 1527.
> java.lang.IllegalThreadStateException: process hasn't exited
>         at java.lang.UNIXProcess.exitValue(UNIXProcess.java:116)
>         at org.apache.derbyTesting.functionTests.tests.derbynet.testconnection.execCmdDumpResults(Unknown
>         at org.apache.derbyTesting.functionTests.tests.derbynet.testconnection.execCmdDumpResults(Unknown
>         at org.apache.derbyTesting.functionTests.tests.derbynet.testconnection.main(Unknown

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message