[omniORB] OmniORB behaviour with firewalls

[Bruce Visscher]

Eric,

We have seen this behavior when we have a VMS server trying to invoke a
callback method on an NT client when the NT client "forgets" to call
BOA::_impl_is_ready.  It's a bug for the client to do this, but it does
seem like this shouldn't hang the server.  This is what Steve Brenneis
was aluding to in
http://www.uk.research.att.com/omniORB/archives/1999-07/0208.html.

Bruce

Eric Dumas wrote:
>=20
> (version used: OmniORB2.6.1)
>=20
> Hello.
>=20
>         We meet currently a problem probably caused by a firewall.
> Here is the architecture:
>=20
> ----------                          ----------
> Component1| <----> Firewall <----> |Component2
> ----------                          ----------
>=20
>         The firewall has been configured to allow Corba
> communications. However... the firewall will cut (disconnect) socket
> connection based on a timeout (5 or 6 minutes). The timeout is not
> based on an activity status... but on a life time of the socket.
>=20
>         In some conditions (when performing a Corba call after the
> timeout, or waiting for the answer from Component2), Component1
> blocks. It may come from the omniORB... does omniORB check a
> socket is still alived when sending data? Has anybody meet this
> kind of problem?
>=20
>         Thank you for your feedback.
>=20
> --
>                         =C9ric Dumas (dumas@tumbleweed.com)
>    Tumbleweed Communication, 700 Saginaw Drive, Redwood City, CA 94063,=
 USA
>                http://www.tumbleweed.com    Tel: +1 650-216-2030