db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fernanda Pizzorno (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1571) NetworkServerControlImpl.consoleExceptionPrintTrace() prints stack trace even when logWriter is null
Date Wed, 26 Jul 2006 11:05:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1571?page=comments#action_12423616 ] 
Fernanda Pizzorno commented on DERBY-1571:

The patch 1571-v2.diff looks good. The test derbynet/ShutDownDBWhenNSShutsDownTest.junit was
failing intermittently with SocketException in Solaris sparc (zones), I have verified that
this patch fixes the problem.

> NetworkServerControlImpl.consoleExceptionPrintTrace() prints stack trace even when logWriter
is null
> ----------------------------------------------------------------------------------------------------
>                 Key: DERBY-1571
>                 URL: http://issues.apache.org/jira/browse/DERBY-1571
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server, Newcomer, Regression Test Failure
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: 1571-v2.diff, 1571.diff
> NetworkServerControlImpl.consoleExceptionPrintTrace() prints the stack
> trace to System.err if logWriter is null. This has occasionally caused
> errors in the regression tests. See
> http://www.multinet.no/~solberg/public/Apache/
> for an example.
> The test failure happens when NetworkServerControlImpl.shutdown() has
> sent the shutdown command and starts a loop calling ping() until it
> gets an error. Since it expects ping() to fail, it sets logWriter to
> null to avoid getting error messages printed on the console.
> In most cases, the network server is already stopped before the first
> call to ping(). Then ping() fails when calling setUpSocket(), and no
> message is printed. On the other hand, if the server is stopped while
> ping() is being executed, the error might occur other places. For
> instance, it might fail with a SocketException in
> fillReplyBuffer(). fillReplyBuffer() then calls clientSocketError(),
> which in turn calls consolePropertyMessage() and
> consoleExceptionPrintTrace().  consolePropertyMessage() correctly
> suppresses the error message, but consoleExceptionPrintTrace() prints
> the stack trace.

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