[omniORB] Closing Idle connections

Serguei Kolos Serguei.Kolos at cern.ch
Mon Jul 7 13:01:35 BST 2003


Hello

May be I misunderstood what the 'idle' connection is, but
from my point of view the following behavior looks strange:

1. I modified the client application from the echo example - now it calls
    the echoString method in a loop once per second
2. I set the ORBinConScanPeriod env. var. to 5 and the ORBtraceLevel to 50
    on the server machine. (All the other config. parameters have their 
default values)
3. I noticed that each 5 seconds the server closes the incoming connection,
    disregarding the fact that the last request has been received via 
that connection
    less then one second ago. The trace output looks like:

omniORB: Scan for idle connections (1057571379,937190000)
omniORB: Scavenger reduce idle count for strand 0x8054b30 to 0
omniORB: Scavenger close connection from giop:tcp:137.138.161.43:40132
omniORB: Scan for idle connections done (1057571379,937190000).
omniORB: throw giopStream::CommFailure from 
giopStream.cc:819(0,NO,COMM_FAILURE_UnMarshalArguments)
omniORB: Server connection refcount = 1
omniORB: Server connection refcount = 0
omniORB: Server close connection from giop:tcp:137.138.161.43:40132
omniORB: Server accepted connection from giop:tcp:137.138.161.43:40133
omniORB: giopWorker task execute.
omniORB: Accepted connection from giop:tcp:137.138.161.43:40133 because 
of this rule: "* unix,ssl,tcp"
omniORB: inputMessage: from giop:tcp:137.138.161.43:40133 348 bytes

Is this an expected behavior or I did something wrong? What does the 
'Idle' mean in this case?

Cheers
Serguei Kolos




More information about the omniORB-list mailing list