web services and ajax: cluster

Showing posts with label cluster. Show all posts

Saturday, March 31, 2012

Web server cluster related problem

We are running an ASP.NET application on a cluster of 3 web-servers, using
the Network Load Balancing feature of Application Center. We have
synchronized the machineKey in machine.config on the 3 web-servers, so we
can utilize a random algorithm for server selection for requests. The
application does not use either session state or application state.

We recently upgraded to .NET Framework 1.1 (including the hotfix for the
"doPostback bug"), and after that we experience a mysterious problem on our
production servers:

Let's call the servers A, B and C. Let's say you select a page (a GET
request), and it is served by either server A or B. The page contains a
form, so when you post it back and server C gets to handle the request, the
response appears to be like the original GET request. The page does not seem
to process the page as a POST request.

The same thing happens if the original page comes from server C, and the
postback is processed by server A or B.

Obviously, it seems that there is something wrong on server C.

We have checked everything we can think of. Among them the .NET Framework
installation, machine.config, and that the web application files are the
same.

Since this is a production environment, we are not allowed to use debug
tools. However, we have enabled tracing. When this problem occurs, we see
that
1) The form collection contains the posted data
2) That LoadViewState and ProcessPostData has been executed, both of which
are not executed on a GET request.
3) SessionId is unchanged

But even so, when the request is processed by the called page, it is
processed as a GET request.

Now I don't know where to keep on looking. Does it ring a bell for anyone?

Thanks,
HelgeAn ASP.NET webform detects if a request is a postback by comparing the
hash value in the viewstate of a page. This hash value is generated
by using a validation key. In the default setting, ASP.NET will
automatically generate an random validation key for each web server.
Thus, sending a POST request to a webform on a different web server
will not be recognized as a POST request because the validation key is
different.

Try changing the machine.config or web.config on each web server to
use a static validation key.

For example,

<machineKey validationKey="Some static key" validation="SHA1"/
Tommy,

"Helge Kalnes" <helge.kalnes@.electricfarm.no> wrote in message news:<ejjxuus#DHA.2072@.TK2MSFTNGP11.phx.gbl>...
> We are running an ASP.NET application on a cluster of 3 web-servers, using
> the Network Load Balancing feature of Application Center. We have
> synchronized the machineKey in machine.config on the 3 web-servers, so we
> can utilize a random algorithm for server selection for requests. The
> application does not use either session state or application state.
> We recently upgraded to .NET Framework 1.1 (including the hotfix for the
> "doPostback bug"), and after that we experience a mysterious problem on our
> production servers:
> Let's call the servers A, B and C. Let's say you select a page (a GET
> request), and it is served by either server A or B. The page contains a
> form, so when you post it back and server C gets to handle the request, the
> response appears to be like the original GET request. The page does not seem
> to process the page as a POST request.
> The same thing happens if the original page comes from server C, and the
> postback is processed by server A or B.
> Obviously, it seems that there is something wrong on server C.
> We have checked everything we can think of. Among them the .NET Framework
> installation, machine.config, and that the web application files are the
> same.
> Since this is a production environment, we are not allowed to use debug
> tools. However, we have enabled tracing. When this problem occurs, we see
> that
> 1) The form collection contains the posted data
> 2) That LoadViewState and ProcessPostData has been executed, both of which
> are not executed on a GET request.
> 3) SessionId is unchanged
> But even so, when the request is processed by the called page, it is
> processed as a GET request.
> Now I don't know where to keep on looking. Does it ring a bell for anyone?
> Thanks,
> Helge
Thanx, but as you can see in my original message we have already done that.
If the machineKeys hadn't been synchronized we would have got an exception.
And in addition when switching between servers A and B there is no problem.
We have of course double checked the machineKeys several times.

I found a KB article
(http://support.microsoft.com/defaul...b;EN-US;323744), but the
problem described here is related ASP.NET 1.0 and is supposed to be fixed in
1.1. I am not able to reproduce a problem as described in this article, but
it is of course possible that the problem is related to this.

:) Helge

"Tommy" <Websoftwares@.Hotmail.com> wrote in message
news:a85edaaf.0402241033.7fa789b8@.posting.google.c om...
> An ASP.NET webform detects if a request is a postback by comparing the
> hash value in the viewstate of a page. This hash value is generated
> by using a validation key. In the default setting, ASP.NET will
> automatically generate an random validation key for each web server.
> Thus, sending a POST request to a webform on a different web server
> will not be recognized as a POST request because the validation key is
> different.
> Try changing the machine.config or web.config on each web server to
> use a static validation key.
> For example,
> <machineKey validationKey="Some static key" validation="SHA1"/>
> Tommy,
> "Helge Kalnes" <helge.kalnes@.electricfarm.no> wrote in message
news:<ejjxuus#DHA.2072@.TK2MSFTNGP11.phx.gbl>...
> > We are running an ASP.NET application on a cluster of 3 web-servers,
using
> > the Network Load Balancing feature of Application Center. We have
> > synchronized the machineKey in machine.config on the 3 web-servers, so
we
> > can utilize a random algorithm for server selection for requests. The
> > application does not use either session state or application state.
> > We recently upgraded to .NET Framework 1.1 (including the hotfix for the
> > "doPostback bug"), and after that we experience a mysterious problem on
our
> > production servers:
> > Let's call the servers A, B and C. Let's say you select a page (a GET
> > request), and it is served by either server A or B. The page contains a
> > form, so when you post it back and server C gets to handle the request,
the
> > response appears to be like the original GET request. The page does not
seem
> > to process the page as a POST request.
> > The same thing happens if the original page comes from server C, and the
> > postback is processed by server A or B.
> > Obviously, it seems that there is something wrong on server C.
> > We have checked everything we can think of. Among them the .NET
Framework
> > installation, machine.config, and that the web application files are the
> > same.
> > Since this is a production environment, we are not allowed to use debug
> > tools. However, we have enabled tracing. When this problem occurs, we
see
> > that
> > 1) The form collection contains the posted data
> > 2) That LoadViewState and ProcessPostData has been executed, both of
which
> > are not executed on a GET request.
> > 3) SessionId is unchanged
> > But even so, when the request is processed by the called page, it is
> > processed as a GET request.
> > Now I don't know where to keep on looking. Does it ring a bell for
anyone?
> > Thanks,
> > Helge

Web server Cluster and SESSION.

Hi everyone,
Will clustering of webservers affect SESSION states?
Is there a dotnet term for the above mentioned scenario?
Pls advise.
Thanks.
Posted Via mcse.ms Premium Usenet Newsgroup Services
----
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----
http://www.mcse.msYou can store your session in a SQL Server such that your web servers all
access the same store, however you have to note that everything you store in
the Session needs to be serialisable for that to work.
"Eric Layman" <namyalcire[at no spam]gmail.com> wrote in message
news:1174907530_3665@.sp6iad.superfeed.net...
> Hi everyone,
> Will clustering of webservers affect SESSION states?
> Is there a dotnet term for the above mentioned scenario?
> Pls advise.
> Thanks.
>
> Posted Via mcse.ms Premium Usenet Newsgroup Services
> ----
> ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
> ----
> http://www.mcse.ms
in this case store the session in SQL
"Eric Layman" <namyalcire[at no spam]gmail.com> wrote in message
news:1174907530_3665@.sp6iad.superfeed.net...
> Hi everyone,
> Will clustering of webservers affect SESSION states?
> Is there a dotnet term for the above mentioned scenario?
> Pls advise.
> Thanks.
>
> Posted Via mcse.ms Premium Usenet Newsgroup Services
> ----
> ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
> ----
> http://www.mcse.ms
Thanks!
But, is this step a must? Since this article was dated 12 Jun 06
http://support.microsoft.com/kb/317604
Currently on .net 1.1
"Aidy" <aidy@.noemail.xxxa.com> wrote in message
news:uNudnTD9nLqeMJrbnZ2dnUVZ8sWhnZ2d@.bt
.com...
> You can store your session in a SQL Server such that your web servers all
> access the same store, however you have to note that everything you store
> in the Session needs to be serialisable for that to work.
> "Eric Layman" <namyalcire[at no spam]gmail.com> wrote in message
> news:1174907530_3665@.sp6iad.superfeed.net...
>
Posted Via mcse.ms Premium Usenet Newsgroup Services
----
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----
http://www.mcse.ms
State Server can also do the job for clustered servers.
ASP.NET applications support maintaining session state on a
centralized session state server *or* on a server running SQL Server.
Because the session state is managed centrally,
any cluster host can recover session state information.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espaol : http://asp.net.do/foros/
===================================
"Aidy" <aidy@.noemail.xxxa.com> wrote in message news:uNudnTD9nLqeMJrbnZ2dnUVZ8sWhnZ2d@.bt
.co
m...
> You can store your session in a SQL Server such that your web servers all
access the same store,
> however you have to note that everything you store in the Session needs to
be serialisable for
> that to work.
> "Eric Layman" <namyalcire[at no spam]gmail.com> wrote in message
> news:1174907530_3665@.sp6iad.superfeed.net...
Eric, please see my just-sent reply.
You can also use ASP.NET's State Server to maintain state in a cluster.
...and, please fix your clock.
You're posting 15 hours into the future. :-)
Thanks.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espaol : http://asp.net.do/foros/
===================================
"Eric Layman" <namyalcire[at no spam]gmail.com> wrote in message
news:1174911829_3689@.sp6iad.superfeed.net...
> Thanks!
> But, is this step a must? Since this article was dated 12 Jun 06
> http://support.microsoft.com/kb/317604
> Currently on .net 1.1
>
> "Aidy" <aidy@.noemail.xxxa.com> wrote in message news:uNudnTD9nLqeMJrbnZ2dn
UVZ8sWhnZ2d@.bt.com...
>
> Posted Via mcse.ms Premium Usenet Newsgroup Services
> ----
> ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
> ---- [url]http://www.mcse.ms[
/url]
"Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
news:uREqFI6bHHA.3648@.TK2MSFTNGP05.phx.gbl...

> State Server can also do the job for clustered servers.
> ASP.NET applications support maintaining session state on a
> centralized session state server *or* on a server running SQL Server.
> Because the session state is managed centrally,
> any cluster host can recover session state information.
Do you have any thoughts as to when to use one and when to use the other...?
There's a fair bit of information on the net about each individually, but
there doesn't seem to be much on which is the more suitable according to
infrastructure etc...
Thanks Juan!
What about implementation of cookies? I doubt cookies has the hassle of
sessions in a web cluster.
Since we are doing it for a company and the company is very strict about its
intellecutal properties; i doubt they are going to let us lay a finger on
their servers.
Im not 15 hours ahead. This is my local time. Its 9pm @. where I'm located
right now. GMT+8
"Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
news:%23sDW5I6bHHA.4808@.TK2MSFTNGP04.phx.gbl...
> Eric, please see my just-sent reply.
> You can also use ASP.NET's State Server to maintain state in a cluster.
> ...and, please fix your clock.
> You're posting 15 hours into the future. :-)
> Thanks.
>
> Juan T. Llibre, asp.net MVP
> asp.net faq : http://asp.net.do/faq/
> foros de asp.net, en espaol : http://asp.net.do/foros/
> ===================================
> "Eric Layman" <namyalcire[at no spam]gmail.com> wrote in message
> news:1174911829_3689@.sp6iad.superfeed.net...
>
>
Posted Via mcse.ms Premium Usenet Newsgroup Services
----
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----
http://www.mcse.ms
re:
> Do you have any thoughts as to when to use one and when to use the other...?[/colo
r]
Couldn't you ask an easier question ?
That's a tough nut to crack.
:-)
All in all, I think it would depend on the size of the cluster.
Small and medium-sized clusters could probably make do with State Server.
For very large, and I mean *very* large, applications in large clusters,
redundant SQL Servers are called for.
That would mean : "a cluster of SQL Servers keeping state for a cluster of w
eb servers".
The scalability of *that* configuration runs into many millions of hits dail
y.
Caveat : when using SQL Server mode, objects stored in session state
are serialised and deserialised when a request is processed.
You cannot store objects which do not support serialisation in session state
,
if you use SQL Server, so that's something to keep in mind when programming.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espaol : http://asp.net.do/foros/
===================================
"Mark Rae" <mark@.markNOSPAMrae.com> wrote in message news:%23VABvO6bHHA.4836@.TK2MSFTNGP03.p
hx.gbl...
> "Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
> news:uREqFI6bHHA.3648@.TK2MSFTNGP05.phx.gbl...
>
> Do you have any thoughts as to when to use one and when to use the other..
.?
> There's a fair bit of information on the net about each individually, but
there doesn't seem to be
> much on which is the more suitable according to infrastructure etc...
>
re:
> What about implementation of cookies? I doubt cookies has the hassle of sessions i
n a web cluster.
You can use both cookies and cookieless sessions.
re:
> Im not 15 hours ahead. This is my local time. GMT+8
This message is stamped a bit after midnight tonight.
:-)
Check your Windows timezone setting.
OE says you posted your message on Mon, 26 Mar 2007 21:10:26 -0700
That's GMT -7, not GMT +8 ( which adds up to the 15 hour difference we're se
eing).
What's your physical location ?
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espaol : http://asp.net.do/foros/
===================================
"Eric Layman" <namyalcire[at no spam]gmail.com> wrote in message
news:1174914330_3705@.sp6iad.superfeed.net...
> Thanks Juan!
> What about implementation of cookies? I doubt cookies has the hassle of se
ssions in a web cluster.
> Since we are doing it for a company and the company is very strict about i
ts intellecutal
> properties; i doubt they are going to let us lay a finger on their servers
.
> Im not 15 hours ahead. This is my local time. Its 9pm @. where I'm located
right now. GMT+8
> "Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
> news:%23sDW5I6bHHA.4808@.TK2MSFTNGP04.phx.gbl...
>
> Posted Via mcse.ms Premium Usenet Newsgroup Services
> ----
> ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
> ---- [url]http://www.mcse.ms[
/url]

Web server Cluster and SESSION.

Hi everyone,

Will clustering of webservers affect SESSION states?

Is there a dotnet term for the above mentioned scenario?

Pls advise.

Thanks.

Posted Via Usenet.com Premium Usenet Newsgroup Services
------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
------------------
http://www.usenet.comYou can store your session in a SQL Server such that your web servers all
access the same store, however you have to note that everything you store in
the Session needs to be serialisable for that to work.

"Eric Layman" <namyalcire[at no spam]gmail.comwrote in message
news:1174907530_3665@.sp6iad.superfeed.net...

Quote:

Originally Posted by

Hi everyone,
>
Will clustering of webservers affect SESSION states?
>
Is there a dotnet term for the above mentioned scenario?
>
Pls advise.
>
Thanks.
>
>
Posted Via Usenet.com Premium Usenet Newsgroup Services
------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
------------------
http://www.usenet.com

in this case store the session in SQL

"Eric Layman" <namyalcire[at no spam]gmail.comwrote in message
news:1174907530_3665@.sp6iad.superfeed.net...

Quote:

Originally Posted by

Thanks!

But, is this step a must? Since this article was dated 12 Jun 06

http://support.microsoft.com/kb/317604
Currently on .net 1.1

"Aidy" <aidy@.noemail.xxxa.comwrote in message
news:uNudnTD9nLqeMJrbnZ2dnUVZ8sWhnZ2d@.bt.com...

Quote:

Originally Posted by

You can store your session in a SQL Server such that your web servers all
access the same store, however you have to note that everything you store
in the Session needs to be serialisable for that to work.
>
"Eric Layman" <namyalcire[at no spam]gmail.comwrote in message
news:1174907530_3665@.sp6iad.superfeed.net...

Quote:

Originally Posted by

>Hi everyone,
>>
>Will clustering of webservers affect SESSION states?
>>
>Is there a dotnet term for the above mentioned scenario?
>>
>Pls advise.
>>
>Thanks.
>>
>>
>Posted Via Usenet.com Premium Usenet Newsgroup Services
>------------------
> ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
>------------------
>http://www.usenet.com

>
>

Posted Via Usenet.com Premium Usenet Newsgroup Services
------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
------------------
http://www.usenet.com
Eric, please see my just-sent reply.
You can also use ASP.NET's State Server to maintain state in a cluster.

...and, please fix your clock.
You're posting 15 hours into the future. :-)

Thanks.

Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espaol : http://asp.net.do/foros/
===================================
"Eric Layman" <namyalcire[at no spam]gmail.comwrote in message
news:1174911829_3689@.sp6iad.superfeed.net...

Quote:

Originally Posted by

Thanks!
>
But, is this step a must? Since this article was dated 12 Jun 06
>
http://support.microsoft.com/kb/317604
>
Currently on .net 1.1
>
>
>
"Aidy" <aidy@.noemail.xxxa.comwrote in message news:uNudnTD9nLqeMJrbnZ2dnUVZ8sWhnZ2d@.bt.com...

Quote:

Originally Posted by

>You can store your session in a SQL Server such that your web servers all access the same store,
>however you have to note that everything you store in the Session needs to be serialisable for
>that to work.
>>
>"Eric Layman" <namyalcire[at no spam]gmail.comwrote in message
>news:1174907530_3665@.sp6iad.superfeed.net...

Quote:

Originally Posted by

>>Hi everyone,
>>>
>>Will clustering of webservers affect SESSION states?
>>>
>>Is there a dotnet term for the above mentioned scenario?
>>>
>>Pls advise.
>>>
>>Thanks.
>>>
>>>
>>Posted Via Usenet.com Premium Usenet Newsgroup Services
>>------------------
>> ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
>>------------------ http://www.usenet.com

>>
>>

>
>
>
Posted Via Usenet.com Premium Usenet Newsgroup Services
------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
------------------ http://www.usenet.com

State Server can also do the job for clustered servers.

ASP.NET applications support maintaining session state on a
centralized session state server *or* on a server running SQL Server.

Because the session state is managed centrally,
any cluster host can recover session state information.

Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espaol : http://asp.net.do/foros/
===================================
"Aidy" <aidy@.noemail.xxxa.comwrote in message news:uNudnTD9nLqeMJrbnZ2dnUVZ8sWhnZ2d@.bt.com...

Quote:

Originally Posted by

Quote:

Originally Posted by

"Eric Layman" <namyalcire[at no spam]gmail.comwrote in message
news:1174907530_3665@.sp6iad.superfeed.net...

Quote:

Originally Posted by

>Hi everyone,
>>
>Will clustering of webservers affect SESSION states?
>>
>Is there a dotnet term for the above mentioned scenario?
>>
>Pls advise.
>>
>Thanks.

"Juan T. Llibre" <nomailreplies@.nowhere.comwrote in message
news:uREqFI6bHHA.3648@.TK2MSFTNGP05.phx.gbl...

Quote:

Originally Posted by

State Server can also do the job for clustered servers.
>
ASP.NET applications support maintaining session state on a
centralized session state server *or* on a server running SQL Server.
>
Because the session state is managed centrally,
any cluster host can recover session state information.

Do you have any thoughts as to when to use one and when to use the other...?

There's a fair bit of information on the net about each individually, but
there doesn't seem to be much on which is the more suitable according to
infrastructure etc...
Thanks Juan!

What about implementation of cookies? I doubt cookies has the hassle of
sessions in a web cluster.

Since we are doing it for a company and the company is very strict about its
intellecutal properties; i doubt they are going to let us lay a finger on
their servers.

Im not 15 hours ahead. This is my local time. Its 9pm @. where I'm located
right now. GMT+8

"Juan T. Llibre" <nomailreplies@.nowhere.comwrote in message
news:%23sDW5I6bHHA.4808@.TK2MSFTNGP04.phx.gbl...

Quote:

Originally Posted by

Eric, please see my just-sent reply.
You can also use ASP.NET's State Server to maintain state in a cluster.
>
...and, please fix your clock.
You're posting 15 hours into the future. :-)
>
Thanks.
>
>
>
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espaol : http://asp.net.do/foros/
===================================
"Eric Layman" <namyalcire[at no spam]gmail.comwrote in message
news:1174911829_3689@.sp6iad.superfeed.net...

Quote:

Originally Posted by

>Thanks!
>>
>But, is this step a must? Since this article was dated 12 Jun 06
>>
>http://support.microsoft.com/kb/317604
>>
>Currently on .net 1.1
>>
>>
>>
>"Aidy" <aidy@.noemail.xxxa.comwrote in message
>news:uNudnTD9nLqeMJrbnZ2dnUVZ8sWhnZ2d@.bt.com...

Quote:

Originally Posted by

>>You can store your session in a SQL Server such that your web servers
>>all access the same store, however you have to note that everything you
>>store in the Session needs to be serialisable for that to work.
>>>
>>"Eric Layman" <namyalcire[at no spam]gmail.comwrote in message
>>news:1174907530_3665@.sp6iad.superfeed.net...
>>>Hi everyone,
>>
>>>Will clustering of webservers affect SESSION states?
>>
>>>Is there a dotnet term for the above mentioned scenario?
>>
>>>Pls advise.
>>
>>>Thanks.
>>
>>
>>>Posted Via Usenet.com Premium Usenet Newsgroup Services
>>>------------------
>>> ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
>>>------------------
>>>http://www.usenet.com
>>>
>>>

>>
>>
>>
>Posted Via Usenet.com Premium Usenet Newsgroup Services
>------------------
> ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
>------------------
>http://www.usenet.com

>
>
>

Posted Via Usenet.com Premium Usenet Newsgroup Services
------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
------------------
http://www.usenet.com
re:

Quote:

Originally Posted by

Do you have any thoughts as to when to use one and when to use the other...?

Couldn't you ask an easier question ?
That's a tough nut to crack.

:-)

All in all, I think it would depend on the size of the cluster.

Small and medium-sized clusters could probably make do with State Server.

For very large, and I mean *very* large, applications in large clusters,
redundant SQL Servers are called for.

That would mean : "a cluster of SQL Servers keeping state for a cluster of web servers".
The scalability of *that* configuration runs into many millions of hits daily.

Caveat : when using SQL Server mode, objects stored in session state
are serialised and deserialised when a request is processed.

You cannot store objects which do not support serialisation in session state,
if you use SQL Server, so that's something to keep in mind when programming.

Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espaol : http://asp.net.do/foros/
===================================
"Mark Rae" <mark@.markNOSPAMrae.comwrote in message news:%23VABvO6bHHA.4836@.TK2MSFTNGP03.phx.gbl...

Quote:

Originally Posted by

"Juan T. Llibre" <nomailreplies@.nowhere.comwrote in message
news:uREqFI6bHHA.3648@.TK2MSFTNGP05.phx.gbl...
>

Quote:

Originally Posted by

>State Server can also do the job for clustered servers.
>>
>ASP.NET applications support maintaining session state on a
>centralized session state server *or* on a server running SQL Server.
>>
>Because the session state is managed centrally,
>any cluster host can recover session state information.

>
Do you have any thoughts as to when to use one and when to use the other...?
>
There's a fair bit of information on the net about each individually, but there doesn't seem to be
much on which is the more suitable according to infrastructure etc...
>

re:

Quote:

Originally Posted by

What about implementation of cookies? I doubt cookies has the hassle of sessions in a web cluster.

You can use both cookies and cookieless sessions.

re:

Quote:

Originally Posted by

Im not 15 hours ahead. This is my local time. GMT+8

This message is stamped a bit after midnight tonight.

:-)

Check your Windows timezone setting.
OE says you posted your message on Mon, 26 Mar 2007 21:10:26 -0700

That's GMT -7, not GMT +8 ( which adds up to the 15 hour difference we're seeing).
What's your physical location ?

Quote:

Originally Posted by

Thanks Juan!
>
What about implementation of cookies? I doubt cookies has the hassle of sessions in a web cluster.
>
Since we are doing it for a company and the company is very strict about its intellecutal
properties; i doubt they are going to let us lay a finger on their servers.
>
Im not 15 hours ahead. This is my local time. Its 9pm @. where I'm located right now. GMT+8
>
"Juan T. Llibre" <nomailreplies@.nowhere.comwrote in message
news:%23sDW5I6bHHA.4808@.TK2MSFTNGP04.phx.gbl...

Quote:

Originally Posted by

>Eric, please see my just-sent reply.
>You can also use ASP.NET's State Server to maintain state in a cluster.
>>
>...and, please fix your clock.
>You're posting 15 hours into the future. :-)
>>
>Thanks.
>>
>>
>>
>Juan T. Llibre, asp.net MVP
>asp.net faq : http://asp.net.do/faq/
>foros de asp.net, en espaol : http://asp.net.do/foros/
>===================================
>"Eric Layman" <namyalcire[at no spam]gmail.comwrote in message
>news:1174911829_3689@.sp6iad.superfeed.net...

Quote:

Originally Posted by

>>Thanks!
>>>
>>But, is this step a must? Since this article was dated 12 Jun 06
>>>
>>http://support.microsoft.com/kb/317604
>>>
>>Currently on .net 1.1
>>>
>>>
>>>
>>"Aidy" <aidy@.noemail.xxxa.comwrote in message news:uNudnTD9nLqeMJrbnZ2dnUVZ8sWhnZ2d@.bt.com...
>>>You can store your session in a SQL Server such that your web servers all access the same
>>>store, however you have to note that everything you store in the Session needs to be
>>>serialisable for that to work.
>>
>>>"Eric Layman" <namyalcire[at no spam]gmail.comwrote in message
>>>news:1174907530_3665@.sp6iad.superfeed.net...
>>Hi everyone,
>>
>>Will clustering of webservers affect SESSION states?
>>
>>Is there a dotnet term for the above mentioned scenario?
>>
>>Pls advise.
>>
>>Thanks.
>>
>>
>>Posted Via Usenet.com Premium Usenet Newsgroup Services
>>------------------
>> ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
>>------------------ http://www.usenet.com
>>
>>
>>>
>>>
>>>
>>Posted Via Usenet.com Premium Usenet Newsgroup Services
>>------------------
>> ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
>>------------------ http://www.usenet.com

>>
>>
>>

>
>
>
Posted Via Usenet.com Premium Usenet Newsgroup Services
------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
------------------ http://www.usenet.com

"Juan T. Llibre" <nomailreplies@.nowhere.comwrote in message
news:OzTLGs6bHHA.1300@.TK2MSFTNGP02.phx.gbl...

Quote:

Originally Posted by

re:

Quote:

Originally Posted by

>Do you have any thoughts as to when to use one and when to use the
>other...?

>
Couldn't you ask an easier question ?

:-)

Quote:

Originally Posted by

Caveat : when using SQL Server mode, objects stored in session state
are serialised and deserialised when a request is processed.
>
You cannot store objects which do not support serialisation in session
state,
if you use SQL Server, so that's something to keep in mind when
programming.

Ah... that sounds like a bit of a "gotcha" - thanks for that...
Thus wrote Mark,

Quote:

Originally Posted by

"Juan T. Llibre" <nomailreplies@.nowhere.comwrote in message
news:uREqFI6bHHA.3648@.TK2MSFTNGP05.phx.gbl...
>

Quote:

Originally Posted by

Do you have any thoughts as to when to use one and when to use the
other...?
>
There's a fair bit of information on the net about each individually,
but there doesn't seem to be much on which is the more suitable
according to infrastructure etc...

StateServer cannot be clustered, so it introduces a single point of failure,
making any cluster in front of it rather moot ;-)

Cheers,
--
Joerg Jooss
news-reply@.joergjooss.de
re:

Quote:

Originally Posted by

StateServer cannot be clustered, so it introduces a single point of failure

Yes. That's why I said that it's only good for small/medium websites
( which don't require clustered web servers... )

Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espaol : http://asp.net.do/foros/
===================================
"Joerg Jooss" <news-reply@.joergjooss.dewrote in message
news:94fc50716ed588c93e0d7f6d3228@.msnews.microsoft .com...

Quote:

Originally Posted by

Thus wrote Mark,
>

Quote:

Originally Posted by

>"Juan T. Llibre" <nomailreplies@.nowhere.comwrote in message
>news:uREqFI6bHHA.3648@.TK2MSFTNGP05.phx.gbl...
>>

Quote:

Originally Posted by

>>State Server can also do the job for clustered servers.
>>>
>>ASP.NET applications support maintaining session state on a
>>centralized session state server *or* on a server running SQL Server.
>>>
>>Because the session state is managed centrally,
>>any cluster host can recover session state information.

>Do you have any thoughts as to when to use one and when to use the
>other...?
>>
>There's a fair bit of information on the net about each individually,
>but there doesn't seem to be much on which is the more suitable
>according to infrastructure etc...

>
StateServer cannot be clustered, so it introduces a single point of failure, making any cluster in
front of it rather moot ;-)
>
Cheers,
--
Joerg Jooss
news-reply@.joergjooss.de
>
>

Yes, it will. Look into two options:
1) ASP.NET State Server
2) SQL Server Session State option
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net
"Eric Layman" wrote:

Quote:

Originally Posted by

Hi everyone,
>
Will clustering of webservers affect SESSION states?
>
Is there a dotnet term for the above mentioned scenario?
>
Pls advise.
>
Thanks.
>
>
>
Posted Via Usenet.com Premium Usenet Newsgroup Services
------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
------------------
http://www.usenet.com
>

Saturday, March 31, 2012

Web server cluster related problem

Web server Cluster and SESSION.

Web server Cluster and SESSION.

web services and ajax

Blog Archive

About Me