Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <13885301.1186011592849.JavaMail.jira@brutus>
Date: Wed, 1 Aug 2007 16:39:52 -0700 (PDT)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2933) When  network server disconnects due
 to an I/O Exception it does not always log the exception that caused the
 error
In-Reply-To: <11051576.1184279884620.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden updated DERBY-2933:
----------------------------------

    Attachment: derby-2933_diff.txt

Here is another attempt at a patch.  I am not really all that pleased with it as I fear it may still gobble some unexpected exceptions.  This patch is the same as the first except for it does not log an exception for 1) SocketExceptions which are usually the client disconnecting.
2)The case where DDMReader.fill() expects bytes but gets none.   This is the case when the database is shutdown.

I'd appreciate if someone can take a look. At least the patch does have the advantage that it will log some of the exceptions that were not being logged before. It is just a question of whether that is good enough.

Kathey


> When  network server disconnects due to an I/O Exception it does not always log the exception that caused the error
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2933
>                 URL: https://issues.apache.org/jira/browse/DERBY-2933
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.2.2.1
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>         Attachments: derby-2933_diff.txt, DERBY-2933_no_commit_diff.txt, derby-2933_stat.txt
>
>
> I found this issue when debugging  my attempted fix for DERBY-2892.  The I/O Exception that occurs in writeScalarStream is not logged.  To reproduce apply the patch in DERBY-2892 and run the repro there.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.