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] Created: (DERBY-3704) 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
Date Tue, 03 Jun 2008 16:30:45 GMT
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
                 URL: https://issues.apache.org/jira/browse/DERBY-3704
             Project: Derby
          Issue Type: Bug
    Affects Versions: 10.5.0.0
            Reporter: Kathey Marsden
            Priority: Minor


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.


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