Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <4100421.1185897655270.JavaMail.jira@brutus>
Date: Tue, 31 Jul 2007 09:00:55 -0700 (PDT)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Assigned: (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 reassigned DERBY-2933:
-------------------------------------

    Assignee: Kathey Marsden

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