[DERBY-4304] Network Server shutdown should handle exceptions and finish the server shutdown completely

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.6.1.0
• Fix Version/s: 10.3.3.1, 10.4.2.1, 10.5.3.1, 10.6.1.0
• Component/s: Network Server
• Assignee: Mamta A. Satoor
• Reporter: Mamta A. Satoor
• Created: 13/Jul/09 18:15
• Updated: 21/Jan/11 17:52
• Resolved: 17/Sep/09 17:59

Description

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.

Issue Links

• is related to: DERBY-4053 Network Server's failure to rollback local transactions on shutdown can cause hang on startup with message java.net.BindException: Address already in use: NET_Bind in derby.log
• is related to: DERBY-4310 Closing a prepared statement with an embedded XAConnection can cause the statement to be reprepared and errors related to missing dependencies. This can interfere with network server closeSession()
• relates to: DERBY-4306 NullPointerException in JMXManagementService.unregisterMBean when running jdbcapi._Suite