Limit Connections
We're just about to put a new application into the live arena and I've been asked to limit the connections initially to ensure the system isn't hammered as soon as we launch.
I'm running W2K Server with IIS5 & SP3.
What I need to know is two fold:
1. Is it just as simply as setting the limit connections number on the Web Site window to say 50? Do I need to stop/start the services for it to take effect? Is it advisable to have it so low? When the limit is reached is it the 500.13 error that is called or the 403 error?
2. I've been using system monitor to monitor the development testing of the application but I was wondering what settings should be added to monitor the amount of connections (not sessions) open at any time.
Thanx
I'm running W2K Server with IIS5 & SP3.
What I need to know is two fold:
1. Is it just as simply as setting the limit connections number on the Web Site window to say 50? Do I need to stop/start the services for it to take effect? Is it advisable to have it so low? When the limit is reached is it the 500.13 error that is called or the 403 error?
2. I've been using system monitor to monitor the development testing of the application but I was wondering what settings should be added to monitor the amount of connections (not sessions) open at any time.
Thanx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Not at all. :o)
Good job CharlyOz.
Thanks for the points and the grade.
Brad
Good job CharlyOz.
Thanks for the points and the grade.
Brad
ASKER
Thanx for the help.
CharlyOz
Interesting script...I'm giving you 50 points for this...hope Brad doesn't mind too much...