[ http://issues.apache.org/jira/browse/DERBY-1694?page=comments#action_12428151 ] Daniel John Debrunner commented on DERBY-1694: ----------------------------------------------
Thanks John, I need to fix up the javadoc and coments in the code. However I think that before my patch that wait=true did not dump output to standard out. It called execCmd which just forks the process, it doesn't perform the extra magic that execCmdDumpResults does to display the output. > derbynet/testProperties.java hangs > ---------------------------------- > > Key: DERBY-1694 > URL: http://issues.apache.org/jira/browse/DERBY-1694 > Project: Derby > Issue Type: Bug > Components: Test > Affects Versions: 10.3.0.0 > Environment: Windows XP IBM 142 JRE > Reporter: Daniel John Debrunner > 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
