You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/06/05 23:13:44 UTC
[jira] Assigned: (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
[ https://issues.apache.org/jira/browse/DERBY-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reassigned DERBY-3704:
-------------------------------------
Assignee: Kathey Marsden
> 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
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3704_diff.txt
>
>
> 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.