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 2006/12/08 11:16:20 UTC
[jira] Created: (DERBY-2166) Implement proper handling of
SoecketTimeoutException in DRDAConnThread
Implement proper handling of SoecketTimeoutException in DRDAConnThread
----------------------------------------------------------------------
Key: DERBY-2166
URL: http://issues.apache.org/jira/browse/DERBY-2166
Project: Derby
Issue Type: Improvement
Reporter: Bernt M. Johnsen
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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489082 ]
Bernt M. Johnsen commented on DERBY-2166:
-----------------------------------------
This issue can't be ported to 10.2 or 10.1 since it needs SocketTimeoutException which was introduced in JDK 1.4 while 10.2 and 10.1 supports JDK 1.3.
> 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.
[jira] Commented: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465798 ]
Bryan Pendleton commented on DERBY-2166:
----------------------------------------
I like the new patch better. The comments make it clearer how the new exception works. There's some tab/space awkwardness in the patch, but other than that I have no additional comments. Thanks for the updated version!
> 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
[jira] Updated: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernt M. Johnsen updated DERBY-2166:
------------------------------------
Attachment: MaxThreadTest.java
derby-2166-v2.stat
derby-2166-v2.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-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
[jira] Commented: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464863 ]
Bryan Pendleton commented on DERBY-2166:
----------------------------------------
I'm having a bit of trouble understanding why this is related to derby.drda.timeSlice. Are you saying that the *only* time we will get this exception is if derby.drda.timeSlice was set?
Also, regarding the change to DRDAConnThread.java, why do you have to catch all DRDAProtocolException and then test to see if you got a DRDASocketTimeoutException? Can you not just specifically catch DRDASocketTimeoutException?
I guess I find it somewhat confusing to make this new exception be a subclass of DRDAProtocolException. It seems like DRDAProtocolException occurrences generally indicate severe bugs in the code, and this new exception seems like it would be a normal occurrence when time slicing.
> 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
[jira] Commented: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464762 ]
Bernt M. Johnsen commented on DERBY-2166:
-----------------------------------------
This patch catches SocketTimeOutException and throws a DRDASocketTimeoutException which is a subclass of DRDAProtocolException which then again is caught in DRDAConnThread.processCommand(). Not the nicest solution, but does the job.
Comments please.
> 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
[jira] Commented: (DERBY-2166) Implement proper handling of
SoecketTimeoutException in DRDAConnThread
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-2166?page=comments#action_12456755 ]
Bernt M. Johnsen commented on DERBY-2166:
-----------------------------------------
SocketTimeoutException was introduced in JDK 1.4
> Implement proper handling of SoecketTimeoutException in DRDAConnThread
> ----------------------------------------------------------------------
>
> Key: DERBY-2166
> URL: http://issues.apache.org/jira/browse/DERBY-2166
> Project: Derby
> Issue Type: Improvement
> Reporter: Bernt M. Johnsen
>
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernt M. Johnsen closed DERBY-2166.
-----------------------------------
> 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
> Assignee: 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.
[jira] Updated: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernt M. Johnsen updated DERBY-2166:
------------------------------------
Derby Info: [Patch Available]
> 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
[jira] Updated: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-2166?page=all ]
Bernt M. Johnsen updated DERBY-2166:
------------------------------------
Summary: Implement proper handling of SocketTimeoutException in DRDAConnThread (was: Implement proper handling of SoecketTimeoutException in DRDAConnThread)
> Implement proper handling of SocketTimeoutException in DRDAConnThread
> ---------------------------------------------------------------------
>
> Key: DERBY-2166
> URL: http://issues.apache.org/jira/browse/DERBY-2166
> Project: Derby
> Issue Type: Improvement
> Reporter: Bernt M. Johnsen
>
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-2166?page=all ]
Bernt M. Johnsen updated DERBY-2166:
------------------------------------
Component/s: Network Server
Assignee: Bernt M. Johnsen
> Implement proper handling of SocketTimeoutException in DRDAConnThread
> ---------------------------------------------------------------------
>
> Key: DERBY-2166
> URL: http://issues.apache.org/jira/browse/DERBY-2166
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Reporter: Bernt M. Johnsen
> Assigned To: Bernt M. Johnsen
>
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernt M. Johnsen resolved DERBY-2166.
-------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: (was: [Patch Available])
> 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.
-
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
[jira] Commented: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Mayuresh Nirhali (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465084 ]
Knut Anders Hatlen commented on DERBY-2166:
-------------------------------------------
In DDMReader, wouldn't it be better to write
catch (SocketTimeoutException ...) {...}
catch (IOException ...) {...}
instead of
catch (IOException ioe) {
if (ioe instanceof SocketTimeoutException) {
...
} else {
...
}
}
?
> 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
[jira] Commented: (DERBY-2166) Implement proper handling of
SocketTimeoutException in DRDAConnThread
Posted by "Mayuresh Nirhali (JIRA)" <ji...@apache.org>.
[ 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.