db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4304) Network Server shutdown should handle exceptions and finish the server shutdown completely
Date Thu, 16 Jul 2009 17:15:14 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732028#action_12732028
] 

Kathey Marsden commented on DERBY-4304:
---------------------------------------

Mamta I noted that at least in the case of DERBY-4310, the exception stack trace does not
print to the console, just the error message.  This is the contents of serverConsole.log:
2009-07-16 17:05:43.546 GMT : Apache Derby Network Server - 10.6.0.0 alpha - (794751) started
and ready to accept connections on port 1527

2009-07-16 17:05:45.078 GMT : Unexpected exception:
 Table/View 'APP.FOO' does not exist.

Can you make it so the full stack trace prints as well. That would be much more helpful. 
To try it out, run jdbcapi.XATest and look at logs/serverConsoleOutput.logs.




> Network Server shutdown should handle exceptions and finish the server shutdown completely
> ------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4304
>                 URL: https://issues.apache.org/jira/browse/DERBY-4304
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Server
>    Affects Versions: 10.6.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>         Attachments: DERBY4304_handleExceptions_patch1_diff.txt
>
>
> While working on DERBY-4053, found that an exception from Connection.close was not handled
properly by the server shutdown code which caused a new instance server startup to hang. Resolved
the problem with Connection close but in general, we should
> 1) Make sure an exception during shutdown processing does not prevent the remaining shutdown
tasks, like closing the server socket from occurring. 
> 2) Make sure any exceptions that occur in shutdown processing are reported to the console.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message