If an IOException is encountered during establishment of the connection, Network Server should print the root exception to the console instead of a generic message

• Key: DERBY-3704
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Minor
• Assignee: Kathey Marsden
• Reporter: Kathey Marsden
• Component/s: Network Server
• Affects Version/s: 10.5.1.1
• Fix Version/s: 10.4.2.0, 10.5.1.1

Description

In working on DERBY-3701, I noticed that when the FileNotFound exception caused the connection to fail it just printed out a generic exception, not the IOException that caused the error.

That is because of this code in ClientThread.
 catch (IOException ioe) {
                    // IOException causes this thread to stop. No
                    // console error message if this was caused by a
                    // shutdown
                    synchronized (parent.getShutdownSync()) {
                        if (!parent.getShutdown()) {
                            parent.consolePropertyMessage("DRDA_UnableToAccept.S");
                        }
                    }

In the event of an unexpected IOException the actual exception should print and the client socket should be closed if it has been established.

Comments

[Kathey Marsden]

Attached is a patch for this issue. I ran the repro for DERBY-3701 to test and verified that the FileNotFoundException printed to the console and the client socket was closed, but that is not a valid long term test because the problem will no longer occur once DERBY-3701 is fixed.