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 Wed, 30 Aug 2006 22:28:22 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1694?page=all ]

Mike Matrigali updated DERBY-1694:
----------------------------------

          Urgency: Urgent
    Fix Version/s: 10.2.1.0

I have now seen the test hang against sun jdk 1.4.2 in a 10.2 client branch.  What I see outside
is the test hangs all night.  I thought it might be firewall related, but the other tests
seem to work, and I just saw the 
hang with firewall completely disabled.  

I am bumping the urgency as it is starting to affect my ability to commit changes into the
codeline as I
lose a day every time I run
The last part in the tmp file is:
Start testProperties to test property priority
Testing derby.properties Port 1528
org.apache.derby.drda.NetworkServerControl start
Successfully Connected
org.apache.derby.drda.NetworkServerControl shutdown
Apache Derby Network Server - 10.2.1.2 beta shutdown at 2006-08-30 19:01:54.666
GMT
Testing System properties  Port 1529
-Dderby.drda.portNumber=1529 org.apache.derby.drda.NetworkServerControl start
Successfully Connected
org.apache.derby.drda.NetworkServerControl shutdown -p 1529
Apache Derby Network Server - 10.2.1.2 beta shutdown at 2006-08-30 19:01:57.170
GMT
Testing command line option. Port 1530
org.apache.derby.drda.NetworkServerControl start -p 1530
Successfully Connected
org.apache.derby.drda.NetworkServerControl shutdown -p 1530
Apache Derby Network Server - 10.2.1.2 beta shutdown at 2006-08-30 19:01:59.773
GMT
Testing start server by specifying system properties without values
First shutdown server started on default port by the test harness
org.apache.derby.drda.NetworkServerControl shutdown -p 1527
Apache Derby Network Server - 10.2.1.2 beta shutdown at 2006-08-30 19:02:01.576
GMT
-Dderby.drda.logConnections -Dderby.drda.traceAll -Dderby.drda.traceDirectory -D
derby.drda.keepAlive -Dderby.drda.timeSlice -Dderby.drda.host -Dderby.drda.portN
umber -Dderby.drda.minThreads -Dderby.drda.maxThreads -Dderby.drda.startNetworkS
erver -Dderby.drda.debug org.apache.derby.drda.NetworkServerControl start
java.lang.Exception: DRDA_NoIO.S:Could not connect to Derby Network Server on ho
st 127.0.0.1, port 1527.
    at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessag
eWork(NetworkServerControlImpl.java:2648)
    at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessag
e(NetworkServerControlImpl.java:1470)
    at org.apache.derby.impl.drda.NetworkServerControlImpl.setUpSocket(NetworkSe
rverControlImpl.java:2049)
    at org.apache.derby.impl.drda.NetworkServerControlImpl.ping(NetworkServerCon
trolImpl.java:827)
    at org.apache.derby.drda.NetworkServerControl.ping(NetworkServerControl.java
:312)
    at org.apache.derbyTesting.functionTests.tests.derbynet.testProperties.waitF
orStart(testProperties.java:218)
    at org.apache.derbyTesting.functionTests.tests.derbynet.testProperties.main(
testProperties.java:297)
org.apache.derby.drda.NetworkServerControl shutdown -p 1527
Could not connect to Derby Network Server on host localhost, port 1527.
org.apache.derby.drda.NetworkServerControl shutdown -p 1528
Could not connect to Derby Network Server on host localhost, port 1528.
org.apache.derby.drda.NetworkServerControl shutdown -p 1529
Could not connect to Derby Network Server on host localhost, port 1529.
org.apache.derby.drda.NetworkServerControl shutdown -p 1530
Could not connect to Derby Network Server on host localhost, port 1530.

> 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

        

Mime
View raw message