Session not available across multiple servers in "InProc" mode

[NAT]

I am using session mode as "InProc"(entered in web.config). I have deployed
my ASP.NET appln. on a server which uses Load Balancer. i.e I have two
servers.
I am using session across pages.The problem I am facing is that sometimes I
find the session and sometimes not. I beleive this is happenning because of
multiple servers. Because session is created on a worker process on one
server and the second time it must be hitting the other server to fetch the
session. Hence the issue.
What is the solution ? Is it possible to acheive this with "InProc" ? Can I
make the application find the session on a particular server . i.e. I should
restrict my application to use session from the worker process from which it
started. Once the application is closed then it can hit any server.But again
should restrict sessions to that server till the application is over. I think
if I can do that then my problem can be solved with "InProc" . But how do I
do this ?
Thanks in advance.

[Winista]

Ask your network admin to make changes in load banalncer/router to make a
user's connection session stick to one server. This way user's call will end
up on same server untill borwser session is closed.

"NAT" <NA*@discussions.microsoft.com> wrote in message
news:5F**********************************@microsof t.com...

I am using session mode as "InProc"(entered in web.config). I have deployed
my ASP.NET appln. on a server which uses Load Balancer. i.e I have two
servers.
I am using session across pages.The problem I am facing is that sometimes
I
find the session and sometimes not. I beleive this is happenning because
of
multiple servers. Because session is created on a worker process on one
server and the second time it must be hitting the other server to fetch
the
session. Hence the issue.
What is the solution ? Is it possible to acheive this with "InProc" ? Can
I
make the application find the session on a particular server . i.e. I
should
restrict my application to use session from the worker process from which
it
started. Once the application is closed then it can hit any server.But
again
should restrict sessions to that server till the application is over. I
think
if I can do that then my problem can be solved with "InProc" . But how do
I
do this ?
Thanks in advance.

[NAT]

Thanks for ur reply, But I cannot do that since this would affect all other
applications running on the server. Is there any other way like changing the
web.config so that this change affects only my appln.
"Winista" wrote:

Ask your network admin to make changes in load banalncer/router to make a
user's connection session stick to one server. This way user's call will end
up on same server untill borwser session is closed.

"NAT" <NA*@discussions.microsoft.com> wrote in message
news:5F**********************************@microsof t.com...

I am using session mode as "InProc"(entered in web.config). I have deployed
my ASP.NET appln. on a server which uses Load Balancer. i.e I have two
servers.
I am using session across pages.The problem I am facing is that sometimes
I
find the session and sometimes not. I beleive this is happenning because
of
multiple servers. Because session is created on a worker process on one
server and the second time it must be hitting the other server to fetch
the
session. Hence the issue.
What is the solution ? Is it possible to acheive this with "InProc" ? Can
I
make the application find the session on a particular server . i.e. I
should
restrict my application to use session from the worker process from which
it
started. Once the application is closed then it can hit any server.But
again
should restrict sessions to that server till the application is over. I
think
if I can do that then my problem can be solved with "InProc" . But how do
I
do this ?
Thanks in advance.

[Peter Bromberg [C# MVP]]

Without a Sticky-IP feature turned on, there's no way to ensure that a user's
next page request will land on the same server where the session originate.

Your alternatives are:
1) State Server.
2) SQL Server.
3) Custom Solution.

Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"NAT" wrote:

Thanks for ur reply, But I cannot do that since this would affect all other
applications running on the server. Is there any other way like changing the
web.config so that this change affects only my appln.
"Winista" wrote:

Ask your network admin to make changes in load banalncer/router to make a
user's connection session stick to one server. This way user's call will end
up on same server untill borwser session is closed.

"NAT" <NA*@discussions.microsoft.com> wrote in message
news:5F**********************************@microsof t.com...

I am using session mode as "InProc"(entered in web.config). I have deployed
my ASP.NET appln. on a server which uses Load Balancer. i.e I have two
servers.
I am using session across pages.The problem I am facing is that sometimes
I
find the session and sometimes not. I beleive this is happenning because
of
multiple servers. Because session is created on a worker process on one
server and the second time it must be hitting the other server to fetch
the
session. Hence the issue.
What is the solution ? Is it possible to acheive this with "InProc" ? Can
I
make the application find the session on a particular server . i.e. I
should
restrict my application to use session from the worker process from which
it
started. Once the application is closed then it can hit any server.But
again
should restrict sessions to that server till the application is over. I
think
if I can do that then my problem can be solved with "InProc" . But how do
I
do this ?
Thanks in advance.