First Last Prev Next    No search results available
Details
: ORB stack overflows with crashes during write()
Bug#: 1222
: TAO
: ORB
Status: RESOLVED
Resolution: FIXED
: All
: All
: 1.2.3
: P3
: major
: ---

:
:
:
: 1202
  Show dependency tree - Show dependency graph
People
Reporter: Carlos O'Ryan <coryan@atdesk.com>
Assigned To: DOC Center Support List (internal) <tao-support@dre.vanderbilt.edu>
:

Attachments
Proposed patches to solve this bug. (88.05 KB, patch)
2002-06-14 12:35, Carlos O'Ryan
Details | Diff


Note

You need to log in before you can comment on or make changes to this bug.

Related actions
Votes: 0


Description:   Opened: 2002-06-12 18:08
This is basically a bug to break apart bug 1202 into more manageable pieces.

Supposed the ORB is running nested event loops to some connection (say the
connections is flow controlled), now suppose the connection is closed by the
peer (for example it crashes.)  The ORB should notify all the queued messages on
that connection about the closure, so the nested event loops can exit.

However, several places in the ORB close the connection and then expect the
destructor of the Transport for notify the queued messages, however, the
destructor won't get called because there are still references to the transport
(in the nested event loops!)

The Nested_Upcall_Crashes test can reproduce this problem (sometimes), I expect
I'll be able to submit patches shortly.
------- Comment #1 From Carlos O'Ryan 2002-06-14 12:35:10 -------
Created an attachment (id=121) [details]
Proposed patches to solve this bug.
------- Comment #2 From Carlos O'Ryan 2002-06-14 13:16:24 -------
Fixed, please read the following ChangeLog entry for all the gory details:
Fri Jun 14 13:58:56 2002  Carlos O'Ryan  <coryan@atdesk.com>
------- Comment #3 From Simon McQueen 2002-08-08 04:33:56 -------
*** Bug 1150 has been marked as a duplicate of this bug. ***

First Last Prev Next    No search results available