[
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_no_commit_diff.txt
Attached is a patch that logs the IO/exceptions and other events that cause
markCommunicationsFailure to be called. This change caused
testNetworkServerSecurityMechanism to start logging this error. I am
investigating that, but the patch to turn on the logging should not be
committed until this is resolved.
testNetworkServerSecurityMechanism(org.apache.derbyTesting.functionTests.tests.derbynet.NSSecurityMechanismTest)
java.lang.Exception: totalBytesRead < minimumBytesNeeded
at org.apache.derby.impl.drda.DDMReader.fill(DDMReader.java:1936)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(DDMReader.java:1651)
at
org.apache.derby.impl.drda.DDMReader.readDssHeader(DDMReader.java:321)
at
org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:677)
at
org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:275)
> 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_no_commit_diff.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.
