[
https://issues.apache.org/jira/browse/DERBY-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117425#comment-13117425
]
Dag H. Wanvik commented on DERBY-5413:
--------------------------------------
Backported and committed on 10.8 as svn 1177352, closing.
Note: I saw during my commit that a change was made to the mergeproperties of
NetCursor.java even though I had made no changes to that file:
Property changes on: java/client/org/apache/derby/client/net/NetCursor.java
___________________________________________________________________
Modified: svn:mergeinfo
Merged
/db/derby/code/trunk/java/client/org/apache/derby/client/net/NetCursor.java:r1177324
Does anyone know why this happens? I see in its mergeinfo patches have been
merged from 10.7 branch as well..
> NetworkServerControl#main can exit with status 1 without printing an error
> message to console
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-5413
> URL: https://issues.apache.org/jira/browse/DERBY-5413
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.8.1.2
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Fix For: 10.8.2.2, 10.9.0.0
>
> Attachments: derby-5413.diff
>
>
> Cf this piece of code in main
> catch (Exception e)
> {
> //if there was an error, exit(1)
> if ((e.getMessage() == null) ||
> !e.getMessage().equals(NetworkServerControlImpl.UNEXPECTED_ERR) ||
> printErrors
> )
> {
> if (server != null)
> server.consoleExceptionPrint(e);
> else
> e.printStackTrace(); // default output stream is System.out
> }
> // else, we've already printed a trace, so just exit.
> System.exit(1);
> The call "server.consoleExceptionPrint(e)" will actually *not* print anything
> unless the debug flag "NetworkServerControlImpl#debugOutput" has ben set to
> true which it isn't a priori.
> I think it should be replaced by a call to
> server.consoleExceptionPrintTrace(e), which will print unconditionally.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
