db-derby-dev mailing list archives

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

     [ https://issues.apache.org/jira/browse/DERBY-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mamta A. Satoor updated DERBY-4304:
-----------------------------------

    Attachment: DERBY4304_handleExceptions_patch1_diff.txt

I have made changes to NetworkServerControlImpl.java so we handle the exceptions during different
steps of server shutdown and continue with the next step in shutdown rather than bailing out
after the first exception. I ran junit suite and didn't see any new failure except the known
intermittent DERBY-4307 (RuntimeinfoTest Assertion failure). I will run derbyall next. If
noone has any comments on the patch, I can check it in later this morning so it can be migrated
to 10.5 codeline before we cut a release candidate there.

> 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
>         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