MBR IT/.NET 247 : ASP Session forwarding on ASPFriends.com 'aspngarchitecture' list

ASP Session forwarding

Messages

Related Types

This message was discovered on ASPFriends.com 'aspngarchitecture' list.

Montgomery, Aiden

-- Moved from [aspngcs] to [aspngarchitecture] by Christie Walker <Click here to reveal e-mail address> --

Hello,

Not sure if this one has been discussed before.

We are moving our ASP.NET applications to run on a cluster. The problem that we have is that this cluster will also be serving the ASP applications. Several of the ASP applications created by other teams use the session state. This works fine in a non-clustered environment. However in the cluster we have the problem that the requests will not be processed by the same machine and hence lose the session.

We are using Application Center 2000 as the cluster controller software. It offers a function called "Enable Web Request Forwarding" which routes the sessions to the machine on which the session was created. This is where our problem lies. We do not desire this function to work with the ASP.NET application (as we want full load balancing and it does not rely on the session state). Does anyone have any experience with this kind of setup?

Is it possible to filter out the ASP.NET applications so that they are not forwarded?

Thanks in advance,

Aiden

Reply to this message...

Dave Cline

You might forgo the "Web Request session forwarding" entirely - allowing
.NET to do its thing. As for you legacy Classic ASP applications - can
you use the internal IP address of one of the nodes in the cluster? Just
avoid the cluster altogether for ASP. Yes it defeats Clustering - but
so does ASP Session.

--
Dave Cline
Click here to reveal e-mail address
www.bangeye.com/
801-796-3413

---- "Montgomery, Aiden" <Click here to reveal e-mail address> wrote:
[Original message clipped]

Reply to this message...

Raghavendra Ural

we had a asp.net application which is load balanced.
We also faced the same session problem.
This is the problem with the config file. In your machine config file you will have machineKey element with an attribute of validationKey="Autogenerate" which will generate its ok key for request. With each request, it checks this validation key. If it is different (in your case from different node) then it will treat the request as a fresh request and creates new session.
so you need to do the following changes in machine.config.
Before
<machineKey validationKey="AutoGenerate" decryptionKey="AutoGenerate" validation="SHA1"/>
Change it to
This is one of the validation key that I have generated from some program.. You can use it.
<machineKey validationKey="EF2E74808CE348777A34240B31C9B64FAC633CB3F493FE6370AF83CD789C9253C2CF8B88908A14C28AF5D9D09EB51BFD7F85C5F72F11A7A71D0D91377F34B709" decryptionKey="9D1CCF73B5DC24A2E042E99F4A11D83CD132CBBB7DC4A962" validation="SHA1"/>

You may have to move to session management in sql server as well.

rgds
Ural
"Montgomery, Aiden" wrote:

[Original message clipped]

Reply to this message...

System.Security.Cryptography.SHA1

MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

	Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
	Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com