[omniORB] Back on the list again...

[Helmut Swaczinna]

Hi everybody,

before im going to talk about our current problem let me say some positiv
words:

Our real complex program system based on omniORB 2.7.1 under Linux works
now in a real-life, commercial environement since several months. It runs
nigth and day, week for week without any crash or the need to shutdown.

Now the "but":

When it is necessary to shutdown the omniORB-processes (e.g. for
configuration 
tasks) after *some weeks* the system shows a very strange behaviour. The 
systemload increases to an exorbitant value. It is nearly impossible to 
execute a command on the console. Shuting down the processes takes up to an
hour on a quit fast machine. Normaly it takes a few seconds. The heavy
systemload is caused by a *very* high traffic rate on the loopback-device. 
There are some hundred million packets delivered during shutdown. During
normal operation there are some million per week. This traffic must be located
in the omniORB-library. There are no extra method-invokations or upcalls in 
the user-code. 

The system consists of 12 omniORB-processes each with about 10 threads
running on one machine. All are combined client/server-processes. The
processes are startet with -ORBinConScanPeriod 0 ans -ORBoutConScanPeriod 0.
Scanning for idle-connections makes the system get instable.

Can somebody explain this strange behaviour to me?

Thanks

Helmut