[omniORB] Exception trying to start new thread

[radamkie at kdm.pl]

Hi Luke,

Thanks for the program. It was really the problem of parameters like 
maxServerThreadPoolSize, threadPerConnectionUpperLimit...etc

I check max number of threads depending on the stack size with Your 
program - results for platform RH Linux AS3 :

Stack size(Kb) Max Threads
=========================
1024           3032
3072           1010
10240(default) 302

...and set accordingly values of these parameters in omniORB.cfg. For 
serwer application I couldn't give too few value of stack size because 
program was
generating other errors.

By optimal settings of stack size and parameters in omniORB.cfg, I made 
test with max load of requests between applications to reach limit of 
threads.
There wasn't "Exception trying to start new thread", but the client 
application
reach 100% of processor utilization and the serwer application after 
some time aborted with such message in trace:

POAPOAPOAPOAPOAPOAPOAPOAAborted

Also, when I stoped the client application, by terminating, I receive 
many such messages:

omniORB: Disable ObjRef(IDL:org/csapi/cs/IpAppChargingSession:1.0) root<3>
omniORB: omniRemoteIdentity deleted.
omniORB: Disable ObjRef(IDL:org/csapi/cs/IpAppChargingSession:1.0) root<3>
omniORB: omniRemoteIdentity deleted.
omniORB: Disable ObjRef(IDL:org/csapi/cs/IpAppChargingSession:1.0) root<3>
omniORB: omniRemoteIdentity deleted.
omniORB: Disable ObjRef(IDL:org/csapi/cs/IpAppChargingSession:1.0) root<3>
omniORB: omniRemoteIdentity deleted.
omniORB: Disable ObjRef(IDL:org/csapi/cs/IpAppChargingSession:1.0) root<3>
omniORB: omniRemoteIdentity deleted.
omniORB: Disable ObjRef(IDL:org/csapi/cs/IpAppChargingSession:1.0) root<3>
omniORB: omniRemoteIdentity deleted.
omniORB: Disable ObjRef(IDL:org/csapi/cs/IpAppChargingSession:1.0) root<3>
omniORB: omniRemoteIdentity deleted.
omniORB: Disable ObjRef(IDL:org/csapi/cs/IpAppChargingSession:1.0) root<3>
omniORB: omniRemoteIdentity deleted.
omniORB: Disable ObjRef(IDL:org/csapi/cs/IpAppChargingSession:1.0) root<3>
omniORB: omniRemoteIdentity deleted.
omniORB: Disable ObjRef(IDL:org/csapi/cs/IpAppChargingSession:1.0) root<3>
omniORB: omniRemoteIdentity deleted.
omniORB: Disable ObjRef(IDL:org/csapi/cs/IpAppChargingSession:1.0) root<3>
omniORB: omniRemoteIdentity deleted.

Why there is so many omniRemoteIdentity to delete? Because of too many 
threads?
And what can be the reason that POAPOA is aborted ?

Regards
Radek



Quoting Luke Deller <ldeller at xplantechnology.com>:

> Hi Radek,
>
> On Fri, 2006-03-31 at 18:32 +0200, radamkie at kdm.pl wrote:
>> The platform is:
>>
>> OS:Red Hat Enterprise Linux AS release 3 (Taroon Update 5)
>> Kernel:Linux 2.4.21-32
>> Processor: Intel(R) Xeon 3GHz
>> RAM: 2GB
>
> I guess from your kernel name that you're running a 32-bit kernel; I
> take it that this model of Xeon doesn't support the EM64T extensions,
> which is a shame.
>
>> #cat /proc/sys/kernel/threads-max
>> 14336
>
> In practice you will be able to create far fewer threads than this in a
> single process using the default thread stack size, particularly if you
> are running a 32-bit kernel.
>
> You can see this using the attached c++ program; it will determine how
> many threads can be created on your system using the default thread
> stack size.
>
>> Is a way to check how many threads are working in omniORB application ?
>
> You could always attach to the process using gdb and type "info
> threads".
>
> I still believe that your problem is that omniORB is set to use too many
> threads.  Have you tried limiting omniORB to using say 100 threads?
> This should stop the error message.  For example you could try:
>
> threadPerConnectionPolicy = 1
> maxServerThreadPoolSize = 100
> threadPerConnectionUpperLimit = 50
> threadPerConnectionLowerLimit = 40
>
> Regards,
> Luke.
>
>
> **********************************************************************************************
>
> Important Note
> This email (including any attachments) contains information which is
> confidential and may be subject to legal privilege.  If you are not
> the intended recipient you must not use, distribute or copy this
> email.  If you have received this email in error please notify the
> sender immediately and delete this email. Any views expressed in this
> email are not necessarily the views of XPlan Technology.
>
> It is the duty of the recipient to virus scan and otherwise test the
> information provided before loading onto any computer system.
> Xplan Technology does not warrant that the
> information is free of a virus or any other defect or error.
> **********************************************************************************************
>
>