[DERBY-4350] javaException is created but not thrown or logged in DRDAConnThread.closeStream(InputStream stream)

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 10.5.3.1, 10.6.1.0
• Component/s: Network Server
• Labels: derby_triage10_8
• Urgency: Normal
• Issue & fix info: Newcomer
• Assignee: Unassigned
• Reporter: Katherine Marsden
• Created: 14/Aug/09 16:32
• Updated: 17/Jun/13 09:19
• Resolved: 31/Aug/11 13:35

Description

I noticed this code in DRDAConnThread.closesStream(InputStream stream)

private static void closeStream(InputStream stream){

try

{ if (stream != null) stream.close(); }

catch (IOException e)

{ Util.javaException(e); }

}

I think the javaException won't be thrown or logged and the underlying IOException will be lost. I have not investigated whether it should be thrown or just logged, but should be addressed with the DERBY-1191 fix.

Issue Links

• duplicates: DERBY-5396 DRDAStatement and DRDAConnThread swallow IOExceptions
• is related to: DERBY-326 Improve streaming of large objects for network server and client
• relates to: DERBY-1191 Some SQLExceptions, for example those generated from BrokeredStatements, do not print to derby.log even when derby.stream.error.logSeverityLevel=0