[
https://issues.apache.org/jira/browse/DERBY-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-4350.
---------------------------------------
Resolution: Duplicate
Resolving as duplicate of DERBY-5396, which fixed the issue reported here
(except the logging part, which is tracked in DERBY-1191), and also a similar
occurrence in DRDAStatement.
> javaException is created but not thrown or logged in
> DRDAConnThread.closeStream(InputStream stream)
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-4350
> URL: https://issues.apache.org/jira/browse/DERBY-4350
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.5.3.1, 10.6.1.0
> Reporter: Kathey Marsden
> Priority: Minor
> Labels: derby_triage10_8
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
