db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mayuresh Nirhali (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2166) Implement proper handling of SocketTimeoutException in DRDAConnThread
Date Mon, 16 Apr 2007 07:22:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489029
] 

Mayuresh Nirhali commented on DERBY-2166:
-----------------------------------------

The fix to the parent issue Derby-1856 was ported to 10.2 and 10.1 trunk. but not this one.
I think, it will be very good if 2166 fix is ported to 10.2 n 10.1.






> Implement proper handling of SocketTimeoutException in DRDAConnThread
> ---------------------------------------------------------------------
>
>                 Key: DERBY-2166
>                 URL: https://issues.apache.org/jira/browse/DERBY-2166
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Server
>            Reporter: Bernt M. Johnsen
>         Assigned To: Bernt M. Johnsen
>             Fix For: 10.3.0.0
>
>         Attachments: derby-2166-v2.diff, derby-2166-v2.stat, derby-2166.diff, derby-2166.stat,
MaxThreadTest.java
>
>
> A timeout is set on the session socket (ClientThread) but the SocketTimeoutException
is not taken care of. Connections is therefore closed down if derby.drda.timeSlice is set
and the client idles longer then the timeslice. See DERBY-1856 for more details.

-- 
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