Issue with omniORB select loop implementation

The SocketCollection::Select() function has a built-in hardcoded 50 
millisecond timeout.  This causes major problems with an application 
that I'm developing that must run on IBM 390 series hardware using linux 
running under VM.

Every linux virtual machine that runs an application using omniORB will 
wake up every 50 milliseconds, decide there is nothing to do and go back 
to sleep.  If more than one omniORB application is running on the Linux 
instance, the problem is compounded.  This activity prevents the linux 
instance from being descheduled by VM because it thinks the instance is 
always busy.  Needless to say, this isn't playing nice in the VM world.

Can anyone give me insight into the need for the 50 millisecond timer in 
the first place and what might happen if I changed it or removed it 
entirely?

-- 
Jon Biggar
Levanta Inc.
[email protected]