[
https://issues.apache.org/jira/browse/DERBY-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731536#action_12731536
]
Kathey Marsden edited comment on DERBY-4304 at 7/15/09 9:39 AM:
----------------------------------------------------------------
Thanks Mamta for making this change. I don't think it should go into to 10.5
until we have analyzed and perhaps resolved some of the new errors that will
show up in the log and console. I think errors like the NullPointerException
unregistering might be disconcerting.
was (Author: kmarsden):
Thanks Mamta for making this change. I don't think it should not go into to
10.5 until we have analyzed and perhaps resolved some of the new errors that
will show up in the log and console. I think errors like the
NullPointerException unregistering might be disconcerting.
> 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.
