Bug 214 - ORB not handling dropped connections correctly
Summary: ORB not handling dropped connections correctly
Status: CLOSED
Alias: None
Product: TAO
Classification: Unclassified
Component: ORB (show other bugs)
Version: 0.4.2
Hardware: x86 Windows NT
: P1 major
Assignee: Carlos O'Ryan
URL:
Depends on:
Blocks:
 
Reported: 1999-08-06 13:39 CDT by Nanbor Wang
Modified: 1999-08-11 12:05 CDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nanbor Wang 1999-08-06 13:39:45 CDT 
Let's say we have a server and client running, where the client is making 100
calls to the server.  If the server is shut down after call 50, call 51 will
fail on the client side and the ORB will report it as COMPLETED=MAYBE.  It will
then fail on the rest of the calls also with COMPLETED=MAYBE.  The ORB should
be able to detect the dropped connection and be able to specify COMPLETED=NO.
Comment 1 Carlos O'Ryan 1999-08-06 23:06:59 CDT 
I'll take care of this one..
Comment 2 Carlos O'Ryan 1999-08-11 10:58:59 CDT 
Testing on UNIX revealed that things are working as expected, will test on NT
now.
Comment 3 Carlos O'Ryan 1999-08-11 11:10:59 CDT 
Just tried on NT, the client gets a TRANSIENT exception (with COMPLETED_NO and a
minor exception that indicates ECONNREFUSED) when the server is down. Notice
that it takes a while for NT to figure out that a local connection is down.
Maybe the problem is not in the ORB but the ImplRepo?
PS: to test this out use the ping/pong test in the Fauls directory. Inserting
code to print the expected exceptions.
Comment 4 Nanbor Wang 1999-08-11 12:05:59 CDT 
Yes, I just checked and this seems like it was fixed since the last time I was
looking into it.