[ http://issues.apache.org/jira/browse/DERBY-1817?page=all ]
Knut Anders Hatlen updated DERBY-1817:
--------------------------------------
Attachment: 1817-4-cleanup.diff
1817-4-cleanup.stat
The attached patch (1817-4-cleanup) contains the cleanup suggested by Bryan. It
is independent of the 1817-3-sync patch, which is not committed yet.
Description:
- moves generation of connection number into addSession()
- adds new method removeThread() which can be used instead of
getThreadList().remove()
- removes methods that are no longer used
- makes methods that are only used by NetworkServerControlImpl private
> 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
> Attachments: 1817-2.diff, 1817-3-sync.diff, 1817-4-cleanup.diff,
> 1817-4-cleanup.stat, 1817.diff, 1817.stat
>
>
> 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
