[omniORB] One client call (JavaIDL) creates 2 incoming calls on server (omniORB 4.0.5), both windows

evgeni.rojkov at durr.com evgeni.rojkov at durr.com
Sat Jul 19 11:07:16 BST 2014

Hello Duncan,
many thanks for the answer.
Was not omniORB or JavaIDL issue.
Some network problem (now solved) was responsible.
Omniorb.log informations was enough right person cares.
Don't have direct contact so don't have more details.
Many thanks for omniORB,

Von: Duncan Grisby [duncan at grisby.org]
Gesendet: Freitag, 18. Juli 2014 16:53
An: Rojkov, Evgeni
Cc: omniORB-list at omniorb-support.com
Betreff: Re: [omniORB] One client call (JavaIDL) creates 2 incoming calls on server (omniORB 4.0.5), both windows

On Thu, 2014-06-26 at 12:58 +0000, evgeni.rojkov at durr.com wrote:

> -      One client call (JavaIDL) creates 2 incoming calls on server
> (omniORB 4.0.5).

Sorry for coming to this late...

There's nothing in omniORB that would cause it to duplicate an incoming
call like that. The client must be doing it. You could perhaps use
wireshark or similar to observe what's going on at a network level.

> -      This client call fails after 5 minutes(!) with
> org.omg.CORBA.COMM_FAILURE (java.io.IOException: An existing
> connection was forcibly closed by the remote host)

That implies that the client thinks the server closed the connection.

> -      Both server calls (answered with about 5K data) get
> giopStream.cc:831(0,NO,COMM_FAILURE_UnMarshalArguments)

That is the normal way that omniORB reports closure of an incoming
connection. It's not directly a sign of a problem. It's only a problem
if the client side doesn't think it has closed the connection.

Can you try to connect to the server with an omniORB client on the same
host as the Java client?  That way you'll get consistent logging out of
omniORB, which might help identify what the issue is.


 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --

More information about the omniORB-list mailing list