[omniORB] COMM_FAILURE on client if outConScanPeriod timeout expire

[Duncan Grisby]

On Monday 26 March, "Enver Cicak" wrote:

> I've server written in c++ and python client. 
> Everything worked fine until I changed following omniORB configuration
> parameters: 
> 
> scanGranularity=1
> inConScanPeriod=15
> outConScanPeriod=10

Did you change the settings on both client and server?

> Then client is able to communicate with server until there is more then
> 10 seconds between calls invoked on server. In that case COMM_FAILURE is
> reported. 
> I use simple retry loop as workaround. Second try always works!

[...]
> <<< Client log >>>

Please can you send a complete client log?  Without that it's impossible
to see what's going on.

[...]
> < Unsuccessful call >
> 
> omniORB: Creating Python ref to unknown: root<0>
> ................................................
> omniORB: LocateRequest to remote: root<0>
> omniORB: sendChunk: to giop:tcp:10.81.2.105:1189 38 bytes
> omniORB: 
> 4749 4f50 0102 0103 1a00 0000 0c00 0000 GIOP............
> 0000 0000 0e00 0000 fee3 de03 4600 000a ............F...
> 1000 0000 0000                          ......
> omniORB: inputMessage: from giop:tcp:10.81.2.105:1189 20 bytes
> omniORB: 
> 4749 4f50 0102 0104 0800 0000 0c00 0000 GIOP............  <-- First call
> had "0200" instead of "0c00"

That number you're looking at is the request id. It is meant to change
with every call.

> 0100 0000                               ....
> omniORB: sendChunk: to giop:tcp:10.81.2.105:1189 60 bytes <-- First call
> had 80B. 

That's because on the first call the client sends codeset information.
On subsequent calls it does not. This has nothing to do with any
COMM_FAILURE you get.

> omniORB: 
> 4749 4f50 0102 0100 3000 0000 0e00 0000 GIOP....0.......
> 0300 0000 0000 0000 0e00 0000 fee3 de03 ................
> 4600 000a 1000 0000 0000 0000 0700 0000 F...............
> 4765 7446 5343 0000 0000 0000           GetFSC......

At this stage, presumably the error occurs. But you haven't copied
omniORB's message about it. Without that I can't help you.

Cheers,

Duncan.

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