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 "Knut Anders Hatlen (JIRA)" <de...@db.apache.org> on 2006/09/07 13:42:24 UTC
[jira] Assigned: (DERBY-1817) Race condition in network server's
thread pool
[ http://issues.apache.org/jira/browse/DERBY-1817?page=all ]
Knut Anders Hatlen reassigned DERBY-1817:
-----------------------------------------
Assignee: Knut Anders Hatlen
Thanks for the useful pointers, Deepa and Bryan. The wiki page was very interesting! I won't address the shutdown and restart problems as part of this issue, but I will take a look at DERBY-1326 later and see if I can come up with a bright idea (or use one of the bright ideas on the wiki page).
> Race condition in network server's thread pool
> ----------------------------------------------
>
> Key: DERBY-1817
> URL: http://issues.apache.org/jira/browse/DERBY-1817
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.2.1.0
> Reporter: Knut Anders Hatlen
> Assigned To: Knut Anders Hatlen
>
> If there is a free DRDAConnThread when a client connects to the network server, the session is put into a queue from which one of the free DRDAConnThreads can pick it up. However, if another client connects after the session was put into the queue, but before the DRDAConnThread has picked it up, one might end up with more sessions in the queue than there are free threads. This can lead to hangs like the ones that we currently see in many of Ole's tests (for instance checkDataSource - http://www.multinet.no/~solberg/public/Apache/TinderBox_Derby/testlog/SunOS-5.10_i86pc-i386/440518-derbyall_diff.txt).
--
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