[
http://issues.apache.org/jira/browse/DERBY-1751?page=comments#action_12433649 ]
Knut Anders Hatlen commented on DERBY-1751:
-------------------------------------------
This test and many others fail intermittently this way because they start a
network server within the test itself. Since the server is running in the same
process as the test, harmless exceptions (caused by the database engine
shutting down at the same time as one of the server threads is closing a
connection) are printed together with the test output. Since these tests are
not testing engine shutdown behaviour, they should ignore server output.
The network server is started like this:
networkServer = new
NetworkServerControl(InetAddress.getByName(hostName),NETWORKSERVER_PORT);
networkServer.start(null);
The null argument given to start() means that console output should be
disabled. However, it doesn't disable all output. Some of the consolePrint*
methods print exceptions to System.err when the console is null. The only way
to make the server completely silent, is to set the console printer to a stream
which just throws away all output. Something like:
PrintWriter pw = new PrintWriter(new OutputStream() { public void write(int
b) { } });
networkServer.start(pw);
> derbynet/testSecMec.java fails with ShutdownException in DerbyNetClient
> framework
> ---------------------------------------------------------------------------------
>
> Key: DERBY-1751
> URL: http://issues.apache.org/jira/browse/DERBY-1751
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.2.1.0
> Environment: JVM: Sun JDK 6 (build 1.6.0-rc-b95)
> OS: Solaris 10 (sparc) local zones
> Hardware: Sun Fire V210 Server, 2 x 1000 MHz CPU
> Reporter: John H. Embretsen
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: derby.log
>
>
> During 10.2.1.0 beta testing this test failed with
> org.apache.derby.iapi.services.context.ShutdownException on 2 of 4 platforms
> running Solaris zones:
> Platform "sparc_zone2":
>
> derbynetclientmats/derbynetmats/DerbyNetClient/derbynetmats/testSecMec.diff
> Platform "sparc_zone3":
>
> derbynetclientmats/derbynetmats/DerbyNetClient/derbynetmats/testSecMec.diff
>
> derbyall/derbynetclientmats/DerbyNetClient/derbynetmats/derbynetmats/testSecMec.diff
> The test did not fail on other platforms, which may indicate timing
> sensitivity (tests are run concurrently in 4 zones (1 global, 3 local) on one
> single machine). Here is one of the diffs (from platform "sparc_zone2"):
> ********* Diff file
> derbynetclientmats/derbynetmats/DerbyNetClient/derbynetmats/testSecMec.diff
> *** Start: testSecMec jdk1.6.0-rc DerbyNetClient derbynetmats:derbynetmats
> 2006-08-14 21:31:48 ***
> 308a309,312
> > java.sql.SQLException: Java exception: ':
> > org.apache.derby.iapi.services.context.ShutdownException'.
> > ... 14 more----------------------------------------------
> > Testing with derby.drda.securityMechanism=INVALID_VALUE
> > EXPECTED EXCEPTION DRDA_InvalidValue.U:Invalid value, INVALID_VALUE, for
> > derby.drda.securityMechanism.
> 310,312d313
> < Testing with derby.drda.securityMechanism=INVALID_VALUE
> < EXPECTED EXCEPTION DRDA_InvalidValue.U:Invalid value, INVALID_VALUE, for
> derby.drda.securityMechanism.
> < -----
> Test Failed.
> *** End: testSecMec jdk1.6.0-rc DerbyNetClient derbynetmats:derbynetmats
> 2006-08-14 21:32:54 ***
> The failure occurred in the DerbyNetClient framework when shutting down the
> database for the second (and last) time in the method
> testUSRSSBPWD_with_BUILTIN(). This test method was added August 9, 2006
> (DERBY-528).
> Attatching derby.log from the failure in derbynetclientmats/derbynetmats on
> sparc_zone2.
--
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
