db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1326) Network server may abandon sessions when Derby system is shutdown and this causes intermittent hangs in the client
Date Thu, 25 May 2006 02:14:30 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1326?page=all ]

Bryan Pendleton updated DERBY-1326:
-----------------------------------

    Attachment: sessionMgmt1.diff

I've been experimenting with the attached patch "sessionMgmt1.diff". In my environment, it
resolves the hang in checkDataSource, and it also passes Deepa's custom "repro1326" test,
even after I modified that test to run the shutdown test case 200 times. So I'm starting to
feel it's pretty reliable as far as avoiding hangs.

However, I'm not completely happy with it. One issue is that I'm still seeing situations in
which a closed() DRDAConnThread is given a non-closed Session to run, which I think is incorrect
behavior (non-closed sessions should only be assigned to non-closed threads).

So I've still got a ways to go on this problem. But since I've had some significant progress,
I wanted to post the work-in-progress changes in order to get feedback, and in order not to
lose them.

Comments and suggestions most welcome!


> Network server may abandon sessions when Derby system is shutdown and this causes intermittent
hangs in the client
> ------------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1326
>          URL: http://issues.apache.org/jira/browse/DERBY-1326
>      Project: Derby
>         Type: Bug

>   Components: Network Server
>     Reporter: Deepa Remesh
>     Assignee: Bryan Pendleton
>  Attachments: repro1326.java, sessionMgmt1.diff
>
> This issue was found when working on DERBY-1219. More details can be found in the comments
at http://issues.apache.org/jira/browse/DERBY-1219

-- 
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


Mime
View raw message