[
https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465710
]
Bernt M. Johnsen commented on DERBY-2166:
-----------------------------------------
I have attached a new version (v2). I decided to keep
DRDASocketTimeoutException as a subclass to DRDAProtocolException, since I
found this the most clean approach to the problem. I tried to make a JUniit
test for this, but there's too much magic going on when running under
BaseJDBCTestCase so I couldn't make it work. Have attached a standalone Jaav
program (MaxThreadsTest.java) which verifies this functionality.
> 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-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.
-
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
