<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body>
I have noticed recently that under different conditions omniORB4 throws different
<br>
exceptions in case when remote server is not running.<br>
<br>
Case 1: my client connects to the server, invokes a method on it and then<br>
waits for a time sufficient for the server to close it's connection
as idle.<br>
If I then kill the server and tell to the client to invoke a
remote method again,<br>
it will get TRANSIENT exception.<br>
Case 2: my client connects to the server, invokes a method on it and then
I kill<br>
the server and tell to the client to invoke a remote method
again.<br>
In this case it will get COMM_FAILURE exception.<br>
<br>
I have raised the issue about these exceptions in the comp.object.corba newsgroup.<br>
Here are my questions the answers of Michi Henning. Do you agree with his
opinion?<br>
Cheers,<br>
Sergei<br>
<pre wrap="">Q:
> For example consider the following situation:
<span class="moz-txt-citetags">> </span> Client invokes two times the same remote method on the same server.
<span class="moz-txt-citetags">> </span> The first invocation is successful. Then the server dies before the <span
class="moz-txt-citetags"></span>client
<span class="moz-txt-citetags">> </span> started the second invocation. Does CORBA spec. provide a clear <span
class="moz-txt-citetags"></span>requirement
<span class="moz-txt-citetags">> </span> to which exception must be thrown?
</pre>
<pre wrap=""><!---->
A:
TRANSIENT. It means "nobody home".
<span class="moz-txt-citetags">
Q:
> </span>Practically I noticed that different ORBs throw different exceptions in
<span class="moz-txt-citetags">> </span>this case.
</pre>
<pre wrap=""><!---->A:
You mean they throw COMM_FAILURE? In that case, the ORB isn't
compliant.</pre>
<br>
</body>
</html>