Re: Number maxim of concurrent conexions
- From: Adam Tauno Williams <adam@xxxxxxxxxxxxxxxx>
- Date: Fri, 25 Aug 2006 08:34:24 -0400
the only place where IDS actually enforces number of connections
is via the NETTYPE parameter in onconfig file. Please see the
manual for more information on this (or past e-mails in this list ... :)
However there are other possible reason for a restriction:
- number of open files when soctcp connection protocol is used,
because for each socket connection a file descriptor is needed.
This usually is an OS parameter.
On Linux you can see this value with "/sbin/sysctl fs.file-max", it is
unlikely to be the issue on a 2.6.x kernel as the default is very high.
Perhaps you can ulimits applied to the Informix user?
- SHM (segment) limitations when ipcshm protocol is used.
Each SHM connection needs some SHM in the "message segment(s)".
If running out of SHM it will impose a limit.
That's what currently comes to my mind.
The actual error and circumstances may reveal more insight.
Same, like the above "/sbin/sysctl kernel.shmmax". But my guess is
NETTYPE values need to be increased.
.
- Prev by Date: Re: Number maxim of concurrent conexions
- Next by Date: Re: Number maxim of concurrent conexions
- Previous by thread: Re: Number maxim of concurrent conexions
- Next by thread: Top 10 stupid things that IT pros still do
- Index(es):
Relevant Pages
|
|
