[ http://issues.apache.org/jira/browse/DERBY-1694?page=all ]
Mike Matrigali updated DERBY-1694: ---------------------------------- I have not seen this test fail since I increased the timeout as part of DERBY-1810. Is this test still failing for anyone since then? In a little debugging of this I think the problem might be related to OS port resources being freed from the previous startup/shutdown of the network server on the default port 1527. There is definitely as separate test issue here, in that once the connect fails the test hangs - but I believe that is purely a test issue and not a product issue. At least for me tests now run so I would not hold up 10.2 for this issue. > derbynet/testProperties.java hangs > ---------------------------------- > > Key: DERBY-1694 > URL: http://issues.apache.org/jira/browse/DERBY-1694 > Project: Derby > Issue Type: Bug > Components: Regression Test Failure > Affects Versions: 10.3.0.0 > Environment: Windows XP IBM 142 JRE > Reporter: Daniel John Debrunner > Fix For: 10.2.1.0 > > Attachments: derby1694diff.txt > > > The testProperties.execCmd() is used to fork a JVM and not handle its > streams. This will cause problems, as indicated by the javadoc for Process. > "The parent process uses these streams to feed input to and get output > from the subprocess. Because some native platforms only provide limited > buffer size for standard input and output streams, failure to promptly > write the input stream or read the output stream of the subprocess may > cause the subprocess to block, and even deadlock" -- 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