[omniORB] Fw: MICO: IDL:omg.org/CORBA/COMM_FAILURE:1.0 (0, maybe-completed)

[Mike Bendickson]

This is a multi-part message in MIME format.

------=_NextPart_000_0030_01BF2B66.60BA3DA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I originally sent this message to the MICO mailing list.  Is this a an
omniORB issue?  I have not seen this problem with my omniORB client.  Is
there a workaround other than doing a retry?

Thanks,
-Mike

----- Original Message -----
From: Kay Roemer <roemer@inf.ethz.ch>
To: <mico-devel@vsb.informatik.uni-frankfurt.de>
Sent: Wednesday, November 10, 1999 6:05 AM
Subject: Re: MICO: IDL:omg.org/CORBA/COMM_FAILURE:1.0 (0, maybe-completed)


>
> > I'm using MICO 2.2.7 on our UNIX platform for a client that communicates
> > with an omniORB2 2.8 server on NT.
> >
> > If my MICO client program is idle for a while (10 minutes or so?) then
the
> > next client request will fail with the following error:
> >
> >         IDL:omg.org/CORBA/COMM_FAILURE:1.0 (0, maybe-completed)
> >
> > Subsequent calls then work until the next idle time.
>
> This is a bug in OmniORB, which closes idle connections after some
> time but doesnt follow the GIOP rules when doing so (i.e., it doesnt
> send a CloseConnection message). Please ask the omniORB people to fix
this.
>
> As a workaround you could try switching off this features in OmniORB, but
> I dont know whether and how this is possible?
>
>
> Kay.
> --
> Kay Roemer          PhD student @ ETH Zurich, Switzerland
> roemer@inf.ethz.ch        http://www.inf.ethz.ch/~roemer/
> "Is there intelligent life on earth?" (Frank Drake, SETI)
>

------=_NextPart_000_0030_01BF2B66.60BA3DA0
Content-Type: text/plain;
	name="Re MICO IDLomg.orgCORBACOMM_FAILURE1.0 (0, maybe-completed).txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="Re MICO IDLomg.orgCORBACOMM_FAILURE1.0 (0, maybe-completed).txt"


> I'm using MICO 2.2.7 on our UNIX platform for a client that =
communicates
> with an omniORB2 2.8 server on NT.
>=20
> If my MICO client program is idle for a while (10 minutes or so?) then =
the
> next client request will fail with the following error:
>=20
>         IDL:omg.org/CORBA/COMM_FAILURE:1.0 (0, maybe-completed)
>=20
> Subsequent calls then work until the next idle time.

This is a bug in OmniORB, which closes idle connections after some
time but doesnt follow the GIOP rules when doing so (i.e., it doesnt
send a CloseConnection message). Please ask the omniORB people to fix =
this.

As a workaround you could try switching off this features in OmniORB, =
but
I dont know whether and how this is possible?


Kay.
--=20
Kay Roemer          PhD student @ ETH Zurich, Switzerland
roemer@inf.ethz.ch        http://www.inf.ethz.ch/~roemer/       =20
"Is there intelligent life on earth?" (Frank Drake, SETI)

------=_NextPart_000_0030_01BF2B66.60BA3DA0--