[omniORB] Interoperability with OpenORB 1.2.0 and omniORB 4 beta

[Sai-Lai Lo]

In future, it is important to report which snapshot of omniORB4 you are
using.
If you use -ORBtraceLevel 2 or above, you will find a line like this in the
output:

omniORB: Distribution date: Mon Sep  3 17:46:21 BST 2001 sll

Then we know how up to date you are with repect to the omniORB4 development.

Any error like this is not good. I would like to know what causes this.

If it is not too much of a problem, could you update your version to the
latest omniORB4 and run your server at -ORBtraceLevel 30. I would like to
see the trace around the point where the error message appears.

Sai-Lai

----- Original Message -----
From: "Jani Niittukari" <jani.niittukari@saraxa.com>
To: "OmniORB Mailing List" <omniorb-list@uk.research.att.com>
Sent: Thursday, September 06, 2001 5:55 PM
Subject: [omniORB] Interoperability with OpenORB 1.2.0 and omniORB 4 beta


> Hi,
>
> We are running omniORB server in Windows 2000. OpenORB client uses the
> server from Linux. Client calls server about 20 times in a minute. The
> system runs several hours and everything is ok, but from time to time I
see
> a error message in OmniORB server's console:
>
> "Detected GIOP 1.2 error in input message, connection is closed"
>
> There is no specific interface call when this happens, it just happens
from
> time to time. I'm not sure but I also remember seeing this when a call was
> made from OmniORB to OpenORB's notification service, but I'm not 100%
sure.
>
> This doesn't seam to be fatal, because the system works nicely after the
> error occurs. What might be the reasons for this error? Should I worry
about
> by own code or is it possibly a marshalling bug in OpenORB or OmniORB?
>
> Thanks,
>
> - Jani
>
>
>