Summary: | Handle leak upon oneway invocation with RW wait startegy | ||
---|---|---|---|
Product: | TAO | Reporter: | ciju john <john_c> |
Component: | ORB | Assignee: | ciju john <john_c> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | mcorino, mitza |
Priority: | P3 | ||
Version: | 1.6.5 | ||
Hardware: | All | ||
OS: | All | ||
Bug Depends on: | 2935 | ||
Bug Blocks: | |||
Attachments: | Demostrate handle loss when making oneway invocation using RW wait startegy. |
Description
ciju john
2007-07-23 11:47:49 CDT
Created attachment 823 [details]
Demostrate handle loss when making oneway invocation using RW wait startegy.
feel free to commit the regression test into the repo. Do you want this be handled as blocker for x.5.10 (you did put severity on blocker)? > ------- Comment #2 from jwillemsen@remedy.nl 2007-07-23 12:45 ------- > feel free to commit the regression test into the repo. Ok. > Do you want this be > handled as blocker for x.5.10 (you did put severity on blocker)? No. I don't think the release should be blocked due to this (this is a corner case that occurs rarely). I will change it to major. A solution for this should refactoring out this code (removing handle from the reactor handle list) from the Transport_Cache and move it completely into the wait strategy. Ciju do you also plan to handle this yourself, if so, please assign the bug to yourself I wasn't planning on it. I just wanted to document this problem (interestingly I found this while debugging a DDS issue). I will accept the bug, but can't say when I will be able to work on it. Ciju still failing with x.5.10 Reassign to john_c@ociweb.com, he indicated he was willing to accept revert change below when fixed Tue Jul 29 18:11:32 UTC 2008 Johnny Willemsen <jwillemsen@remedy.nl> * bin/tao_orb_tests.lst: TAO/tests/Bug_3000_Regression fails because that issue remains unresolved, added !FIXED_BUGS_ONLY. Activated this test on all builds and it runs perfectly as far as I can tell. It seems recent changes to RW strategy (and/or other changes since the submit of this bug) have resolved this issue. |