Problems with ASP.Net Public Service

Question

We have an ASP.Net 2.0 web application running in a web farm that uses the ASP.Net state service to store sessions.

We had problems with the service intermittently and some things have changed, such as machineKey in machine.config.

My actual question is about monitoring the public service. We have all 4 available performance counters that run on the server hosting the service, and so far we have not seen a single session. We also saw how the number of active sessions slowly grows over time, but does not decrease.

Does the public service know when to wait for a session? Is there something we have to do manually?

Edit: We refused public service and left with SQL Server sessions.

To answer the questions below, it seems that the sessions grow forever until the service crashes, and it is very doubtful that any oen flows are connected to the state server. This is a pretty simple web application at the end of the day.

It seems from the reading I am doing that many other people experience similar things, but there seems to be a general lack of common sense and knowledge in any of the reactions in question.

MS seems to have almost no documentation on this topic.

Answer 1

ASP.Net web.config machine.config. , , 20 . machine.config , , , , web.config, .

, , -?

20 , .

? , , , , - .

Answer 2

-, , ? - , , ? expeireince, - - , .

Answer 3

, SQL Server - , .

, , . Velocity, .
, ( ) NCache

, .

SQL Server, , ( , - , -, )

Answer 4

, , .

, , - - . , - .

. , ( ) . , - . -, , , . , ( 20 ) . , , - , , , / , ( -).

, , "" . - , , , :

<sessionState 
   mode="StateServer" 
   stateConnectionString="tcpip=10.1.1.1:55455" 
   cookieless="false" 
   timeout="20" />

Also make sure that you do not override your web.config file so that your machine.config has a longer timeout.