EAServer uses thread pooling rather than a thread-per-client model. Thread pooling allows more clients to connect than threads. Threads are created at server start-up, up to a specified maximum number. EAServer maintains separate thread pools for processing HTTP requests, IIOP requests, and internal processes that are not driven by client requests (services, garbage collection, and so forth). If the thread pools are too small, the server refuses client requests. If the size is too large, memory is wasted.
You can configure these properties to size thread pools:
Property |
EAServer Manager location |
Full name |
|---|---|---|
HTTP threads |
Server Properties/HTTP Config, Maximum Threads |
|
IIOP threads |
Server Properties/Resources, Max Number Client Sessions |
|
Maximum threads |
Server Properties/Resources, Max Number Threads |
