[ 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 10x86.
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: 10.1.0.0
> 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
> Source)
> at
> org.apache.derbyTesting.functionTests.tests.derbynet.testconnection.execCmdDumpResults(Unknown
> Source)
> at
> org.apache.derbyTesting.functionTests.tests.derbynet.testconnection.main(Unknown
> Source)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
