[
https://issues.apache.org/jira/browse/DERBY-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2933:
----------------------------------
Priority: Minor (was: Major)
Unassigning myself from this issue and reducing to minor. I fixed the error to
log in writeScalarStream but there are still occassions where
markCommunicationsFailure is called without logging, most notably when the
server is brought down and active sessions are terminated. I left this as is.
I am not sure if unexpected exceptions might still be left unlogged, so I am
leaving this open.
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
> 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.
