db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1694) derbynet/testProperties.java hangs
Date Mon, 18 Sep 2006 16:00:00 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1694?page=all ]

Mike Matrigali updated DERBY-1694:

I ran full set of  successful tests against ibm 1.4.2 with the derby1694.p2.diff.txt.  The
changes as described seem like an improvement to the current tests so I would be happy to
commit these, let me know if you want this first patch committed or if I should wait for other
comments/changes to other tests.
I welcome any incremental improvement to these network server tests which often intermittently
fail in 
my environment.  This test run was actually first in my last 6 or 7 that had no network server
intermittent failures -- probably more related to my particular netork than this patch.  

> 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:
>         Environment: Windows XP  IBM 142 JRE
>            Reporter: Daniel John Debrunner
>             Fix For:
>         Attachments: derby1694.p2.diff.txt, derby1694.p2.stat.txt, 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


View raw message