Re: How to achieve per ORB/thread client connection timeouts

Am 07.07.2026 um 15:04 schrieb Thomas Braun via omniORB-list:
> Am 19.06.2026 um 10:30 schrieb Duncan Grisby:
>> On Thu, 2026-06-18 at 22:42 +0200, Thomas Braun via omniORB-list wrote:

[...]

>> I take it from the numbers you show that you want to allow opening a
>> new connection to the overloaded server to take a lot longer than
>> normal. Is it really the case that you need to give it such a long time
>> just to accept the new incoming connection, or do you really need an
>> overall long timeout for the call?
> 
>  From my understanding we want to have a connection timeout. The use 
> case is one server which, when the whole distributed system is 
> restarted, has much more than 10k clients trying to connect to it. And 
> that can get slowish...
And I forgot to ask for server tuning knobs. From the 4.5 Server side 
options [1] we currently set [2]

{"maxServerThreadPoolSize", "100"},
{"threadPerConnectionUpperLimit", "55"},
{"threadPerConnectionLowerLimit", "50"},
.

My hunch would be that the thread pool size upper limit 
(maxServerThreadPoolSize) should be larger or?

[1]: https://omniorb.net/omni43/omniORB/omniORB004.html#sec66
[2]: 
https://gitlab.com/tango-controls/cppTango/-/blob/main/src/server/UtilInternal.cpp#L512