[omniORB] Problems when the process limit is reached

Ollis, Gail gail.ollis@roke.co.uk
Tue, 28 Aug 2001 10:53:59 +0100


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	charset="iso-8859-1"

I am finding that my object implementation on Linux hangs up rather than reporting an exception when it hits the user's process limit. I have reproduced the problem with a small change to the "echo" example eg2_clt/eg2_impl:

echo.idl: 
Add a second parameter, "in short pause", to the echostring operation.

eg2_impl.cc:
Modify the echostring implementation to sleep for the number of seconds specified by "pause" before responding (so that the threads for a number of echostring calls can be present simultaneously). 

eg2_clt: 
Call echostring with a 2 second pause.

... and run with uname -p set such that the process limit will be reached if more than one call to echostring is in progress at a time.


Consecutive runs of eg2_clt work OK. However, if it is run a number of times simultaneously (so that threads are present for multiple echostring calls and the thread limit is reached): 
- The first client to run after the limit is reached gets a COMM_FAILURE and terminates.
- All subsequent clients fail get an echostring response or to terminate.
- The implementation does not terminate.


Thanks very much for any help.
Gail.


--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="RMRL-Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="RMRL-Disclaimer.txt"

The information contained in this e-mail and any attachments is confidential to Roke 
Manor Research Ltd and must not be passed to any third party without permission. This 
communication is for information only and shall not create or change any contractual 
relationship.

--------------InterScan_NT_MIME_Boundary--