Two versions of same asp.net app using same server as stateserver - bad?

Posted by MGOwen on Stack Overflow See other posts from Stack Overflow or by MGOwen
Published on 2010-04-23T05:51:07Z Indexed on 2010/04/23 5:53 UTC
Read the original article Hit count: 304

Filed under:
|

We have 2 production web servers for our web app, load balanced to handle lots of traffic.

We also have a similar setup for testing.

Test pool:    [TEST 1]---[TEST 2] 

Prod pool:    [PROD 1]---[PROD 2]

When comparing the Web.Config of the app versions (test vs live) I discovered something surprising: both pools have the same value for stateConnectionString. If I understand right, this means they are using the same state server:

<sessionState 
mode="StateServer" 
stateConnectionString="tcpip=123.123.123.123:42424"
cookieless="false" 
timeout="30"/>

Is this a problem? (How does the state server not confuse the two pools)?

I was having odd only-sometimes slowdown/errors on the test server, that's why I was looking at this in the first place, but the prod pool runs fine...

© Stack Overflow or respective owner

Related posts about load-balancing

Related posts about stateserver