Sessions - Sockets relationship

I’ve got a webapp that runs as standalone on https protocol. Sometimes, when there were plenty of sessions, the app doesn’t respond to the new sessions.
Trying to solve the trouble, using the Command-Line Parameters, I’ve got increased the MaxSecureSockets from the default value of 200 to a new value as 9999; the problem seems solved.
Now I would like understand the relationship between sessions (or somethings else) and the number of the open sockets.
Is there a way to count/monitor open sockets?
When a socket will be closed/released?

Pietro

  1. Sessions are roughly equal to the number of connected users. (Unless you’re leaking sessions)
  2. Each connected session has one or more sockets at any given time. Usually between 2 and 4.
  3. Currently sockets are used for a single http request and discarded.
  4. There is currently no way to monitor the number of open sockets.

BTW, be careful setting the number of sockets so high. When more users can connect, more sessions are created and more memory is used. Your app could more easily run out of RAM.

[quote=353928:@Greg O’Lone]0. Sessions are roughly equal to the number of connected users. (Unless you’re leaking sessions)
0. Each connected session has one or more sockets at any given time. Usually between 2 and 4.
0. Currently sockets are used for a single http request and discarded.
0. There is currently no way to monitor the number of open sockets.

BTW, be careful setting the number of sockets so high. When more users can connect, more sessions are created and more memory is used. Your app could more easily run out of RAM.[/quote]

Many thanks Greg for your explations. Now the “Sessions - Sockets relationship” it’s a little bit clear.