db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2166) Implement proper handling of SocketTimeoutException in DRDAConnThread
Date Tue, 16 Jan 2007 10:04:27 GMT

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

Bernt M. Johnsen commented on DERBY-2166:

Thanks for the comments.
Bryan: setSoTimeout() is done in the client thread on the socket only if timeSlice is set,
so we will get SocketTimeoutException only in that case in DDMReader.

Bryan & Knut: All your commets are of course right and I will rewrite my patch.

> 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
>         Attachments: derby-2166.diff, derby-2166.stat
> 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.
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message