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 "Mayuresh Nirhali (JIRA)" <ji...@apache.org> on 2007/04/09 11:26:32 UTC
[jira] Commented: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487513 ]
Mayuresh Nirhali commented on DERBY-2166:
-----------------------------------------
I downloaded the repro and tried it on latest trunk.
The repro FAILs on trunk. Are there any special config/seetings needed ??
I tried to play around with the waitForSeconds values to see if I was hitting any race condition, but this test failed consistently for me.
here is the output,
<snip>
Apache Derby Network Server - 10.3.0.0 alpha - (526662M) started and ready to accept connections on port 1527 at 2007-04-09 09:18:26.286 GMT
Max threads changed to 1.
Apache Derby Network Server - 10.3.0.0 alpha - (526662M) shutdown at 2007-04-09 09:18:32.651 GMT
Apache Derby Network Server - 10.3.0.0 alpha - (526662M) started and ready to accept connections on port 1527 at 2007-04-09 09:18:32.842 GMT
Time slice changed to 500.
Max threads changed to 1.
FAILED!
Apache Derby Network Server - 10.3.0.0 alpha - (526662M) shutdown at 2007-04-09 09:18:37.475 GMT
</snip>
> 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.