Re: spurious COMM_FAILURE when using fixed ports
Michael Teske via omniORB-list <[email protected]> Thu, 22 Jan 2026 10:13:36 +0100
| Newsgroups | gmane.comp.corba.omniorb.user |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============3972919267440784722==
Content-Type: multipart/alternative;
boundary="------------1UJZF646p3Bp4W0wZBUk9A5g"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------1UJZF646p3Bp4W0wZBUk9A5g
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Hi,
now I understand at least the working case from the example. The client calls sendCloseConnection
from giopServer.cc (because the client is the "server" (corba-wise) for the callback connection), which is not trace-logged unfortunately.
The server gets this message but does not process it yet. It will be done later, when it tries to send the next callback on the same connection
to the next instance of the client which used the same callback port, in giopImpl12::inputQueueMessage.
This leads to the already mentioned output from the server:
omniORB: (5) 2026-01-21 10:34:09.773590: Reset rope addresses (current address giop:tcp:[::1]:53234)
omniORB: (5) 2026-01-21 10:34:09.773595: Orderly connection shutdown: giop:tcp:[::1]:53234 <-------
omniORB: (5) 2026-01-21 10:34:09.773599: throw giopStream::CommFailure from giopImpl12.cc:192(1,NO,COMM_FAILURE_WaitingForReply)
This is not forwarded to the caller but instead the connection is re-established as it should be.
What's left is to find out, what happens in our case where we get
>
> omniORB: (199) 2026-01-21 10:04:51.861953: Reset rope addresses (current address giop:tcp:[::1]:53234)
> omniORB: (199) 2026-01-21 10:04:51.861962: Error in network receive (start of message): giop:tcp:[::1]:53234
> omniORB: (199) 2026-01-21 10:04:51.861966: throw giopStream::CommFailure from giopStream.cc:857(0,MAYBE,COMM_FAILURE_WaitingForReply)
>
I'll put some more log in the lib and let you know about what I found out.
Regards, Michael
--------------1UJZF646p3Bp4W0wZBUk9A5g
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi,</p>
<p><br>
</p>
<p>now I understand at least the working case from the example. The
client calls <span
style="background-color:#ffffff;padding:0px 0px 0px 2px;"><span
style="color:#000000;background-color:#ffffff;font-family:"Monospace";font-size:11pt;white-space:pre;"><span
style="background-color:#d4d4d4;text-decoration:underline;text-decoration-style:solid;text-decoration-color:#0066cc;color:#0066cc;">sendCloseConnection</span></span></span></p>
<p>from giopServer.cc (because the client is the "server"
(corba-wise) for the callback connection), which is not
trace-logged unfortunately.</p>
<p>The server gets this message but does not process it yet. It will
be done later, when it tries to send the next callback on the same
connection</p>
<p>to the next instance of the client which used the same callback
port, in <span
style="background-color:#ffffff;padding:0px 0px 0px 2px;"><span
style="color:#000000;background-color:#ffffff;font-family:"Monospace";font-size:11pt;white-space:pre;"><span
style="color:#268bd2;background-color:#d4d4d4;">giopImpl12</span>::<span
style="text-decoration:underline;text-decoration-style:solid;text-decoration-color:#0066cc;color:#0066cc;">inputQueueMessage</span></span></span>.</p>
<p>This leads to the already mentioned output from the server:</p>
<p>omniORB: (5) 2026-01-21 10:34:09.773590: Reset rope addresses
(current address giop:tcp:[::1]:53234)<br>
omniORB: (5) 2026-01-21 10:34:09.773595: Orderly connection
shutdown: giop:tcp:[::1]:53234 <-------<br>
omniORB: (5) 2026-01-21 10:34:09.773599: throw
giopStream::CommFailure from
giopImpl12.cc:192(1,NO,COMM_FAILURE_WaitingForReply) </p>
<p>This is not forwarded to the caller but instead the connection is
re-established as it should be.</p>
What's left is to find out, what happens in our case where we get
<blockquote type="cite"
cite="mid:[email protected]">
<p> omniORB: (199) 2026-01-21 10:04:51.861953: Reset rope
addresses (current address giop:tcp:[::1]:53234)<br>
omniORB: (199) 2026-01-21 10:04:51.861962: Error in network
receive (start of message): giop:tcp:[::1]:53234<br>
omniORB: (199) 2026-01-21 10:04:51.861966: throw
giopStream::CommFailure from
giopStream.cc:857(0,MAYBE,COMM_FAILURE_WaitingForReply)</p>
</blockquote>
<p>I'll put some more log in the lib and let you know about what I
found out.</p>
<p>Regards, Michael</p>
</body>
</html>
--------------1UJZF646p3Bp4W0wZBUk9A5g--
--===============3972919267440784722==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
omniORB-list mailing list
[email protected]
https://www.omniorb-support.com/mailman/listinfo/omniorb-list
--===============3972919267440784722==--