db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@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
Date Mon, 06 Jul 2009 17:41:14 GMT

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

Rick Hillegas updated DERBY-2933:
---------------------------------

    Issue & fix info: [Repro attached]
             Urgency: Normal

Triage for 10.5.2: Assign normal urgency; note that has reproducible test case.

> 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
>            Priority: Minor
>         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.


Mime
View raw message