Bug 266 - Implement exception handling for Asynchronous Messaging
Summary: Implement exception handling for Asynchronous Messaging
Status: RESOLVED FIXED
Alias: None
Product: TAO
Classification: Unclassified
Component: ORB (show other bugs)
Version: 1.0.2
Hardware: All All
: P2 normal
Assignee: Michael Kircher
URL:
Depends on: 175
Blocks:
  Show dependency tree
 
Reported: 1999-08-26 10:30 CDT by Carlos O'Ryan
Modified: 2000-06-16 17:09 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 Carlos O'Ryan 1999-08-26 10:30:06 CDT 
We have not implemented exception handling for asynchronous invocations.
Comment 1 Michael Kircher 1999-09-08 13:03:59 CDT 
I will accept this one but need to discuss this with Carlos.
Comment 2 Samir Shaikh 2000-05-26 13:00:31 CDT 
Guess this is an important feature thats missing and hence almost renders AMI 
unusable!!!
Comment 3 Carlos O'Ryan 2000-05-26 15:50:33 CDT 
The last comment is not completely accurate (or helpful), exception handling
does work, the only case that fails is when the server crashes during an AMI
invocation.  Maybe Michael can fix this up?
Comment 4 Michael Kircher 2000-06-05 07:44:20 CDT 
I will look into it and see what I can do.

Exception handling in general is available now, but I guess we do not
inform the Reply Handler if we are unable to send the request.

Carlos suggested:
  What we should do is send a message to the transport mux strategy,
saying something like "your connection is going down", the transport
mux strategy can send a message to each one of the Reply_Dispatchers,
saying "the connection is down".  The Synch reply dispatchers can then
simply set a flag, wake up the waiting thread and then the waiting
thread raises COMM_FAILURE.  The ASynch reply dispatchers can invoke
the ReplyHandler with the correct exception too.
Comment 5 Carlos O'Ryan 2000-06-15 20:45:36 CDT 
During my fixes to bug 175 I discovered that this two are related.
I will try to solve as much of this bug (266) as I go along 175
Comment 6 Carlos O'Ryan 2000-06-16 17:05:53 CDT 
The bug as originally described has been fixed.
AMI callbacks still have problems with CloseConnection messages, as described
in bug 124
Comment 7 Carlos O'Ryan 2000-06-16 17:09:56 CDT 
It should have been marked fixed in the last change.