Re: Limiting number of server connections

Hi,

Amir Tal wrote:
> running lotus 6.5 on suse enterprise 8.
> when looking at the server connections in lotus admin client, some users 
> have up to 50 (?!) connections
> open, which causes the server to choke, and crash after 4-5 hours of 
> operation..
> looking at the operating system level tasks using "ps aux" the number of 
> tasks is huge, and gets to several hundreds.
> the machine is an IBM x345 server, which is a pretty powerful hardware, 
> and it manages to carry the load, unlike the
> lotus server itself, which crashes, and send me a "server restart 
> notification" every few hours, after restarting.
> also, while running, the connection to the server is very unstable, and 
> it drops users all the time. sessions are being dropped, address book
> cannot be displayed while working on the server copy, and "unable to 
> find path to server" error messages are appearing often.
> 
> an interesting point is that if you look at the port numbers next to the 
> connections in domino, you'll see that they are in an ascending
> order, as if the previous session got dropped, and the users tries to 
> open the next session on the next port.
> 

We have similar experiences, but we run Domino on Redhat Enterprise, not 
Suse. But maybe it helps...
Problem here was limited number of maximum open files for an user.
So, as which user are you running domino and how many files can he open 
simultaneously?
do:
su - [username]
ulimit -a|grep files

It can be changed in
/etc/security/limits.conf

Usually the limit for an user is 1024 which is far to small but I guess 
Suse has set this right if you run the suse packet?!

Rainer