You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bernt M. Johnsen (JIRA)" <ji...@apache.org> on 2007/01/15 13:38:27 UTC

[jira] Updated: (DERBY-2166) Implement proper handling of SocketTimeoutException in DRDAConnThread

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

Bernt M. Johnsen updated DERBY-2166:
------------------------------------

    Attachment: derby-2166.stat
                derby-2166.diff

> 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