[omniORB] FW: Elötte olvasd el

[Duncan Grisby]

On Friday 7 January, zoltan.sebestyen@netvisor.hu wrote:

>  The push-supplier [the server] and the EventService process resides on the
> same machine which is a Sun box. The server is implemented in ORBacus,
> formerly known as omniBroker.
> The push-consumer (the client) is on another Sun box, a Sun Solaris 2.6. The
> client is implemented in omniORB 2.8.0.
>  So, we want to use the EventService to receive alarm mesages from the
> server. Our problem is the following: if there's no alarm generated for a
> certain amount of time (ca. 5 min) the consumer receives a
> disconnect_push_consumer message, exactly at the same time when the server
> generates the next alarm message, the first one after the silent period.

My only guess as to the problem is that ORBacus is confused by omniORB
closing the TCP connection. If there is no traffic on a TCP connection
for a while, omniORB closes it, as it is permitted to do by the
specification. Try running the omniORB program with a command line
argument of -ORBscanGranularity 0 to see if that helps.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --