Strange web garden problem.... :(

[Victor]

I have a strange problem in my website. I configured my website to run under
2 worker processes. (web garden enabled). and I stored my user information
in the current httpcontext(lik e
Httpcontext.cur rent.items.add( "__currentuser" , myUserobject") and retrieve
the user object like (user =
(UserType)Httpc ontext.current. items["__currentu ser"]). the website
authentication based on the form authentication. and I used login control
and customized the validation method.

No the bloody problem is. I opened two IE windows. and try to log into the
website using two separate account ([e-mail] and [e-mail]). the login process
is successful, but after that, the two IE windows both display the
information for [e-mail] (instead of one for [e-mail] one for [e-mail]).
Is that anything related with web garden..?

I think the two IE windows should be two separated requests, so that
httpcontexts for two browsers should be different. am I rite?

cheers

[bruce barker]

if you use cookies, and start a browser instance from the same root (new
tab, new window, link on desktop) they share the same session cookie,
and thus changing one changes all.

-- bruce (sqlwork.com)

Victor wrote:

I have a strange problem in my website. I configured my website to run under
2 worker processes. (web garden enabled). and I stored my user information
in the current httpcontext(lik e
Httpcontext.cur rent.items.add( "__currentuser" , myUserobject") and retrieve
the user object like (user =
(UserType)Httpc ontext.current. items["__currentu ser"]). the website
authentication based on the form authentication. and I used login control
and customized the validation method.

No the bloody problem is. I opened two IE windows. and try to log into the
website using two separate account ([e-mail] and [e-mail]). the login process
is successful, but after that, the two IE windows both display the
information for [e-mail] (instead of one for [e-mail] one for [e-mail]).
Is that anything related with web garden..?

I think the two IE windows should be two separated requests, so that
httpcontexts for two browsers should be different. am I rite?

cheers

[Victor]

So for the httpcontext, all infomation will be stored in the cookie?
Is there another way to store the current context infomation?
cheers
"bruce barker" <no****@nospam. comwrote in message
news:uR******** ******@TK2MSFTN GP06.phx.gbl...

if you use cookies, and start a browser instance from the same root (new
tab, new window, link on desktop) they share the same session cookie, and
thus changing one changes all.

-- bruce (sqlwork.com)

Victor wrote:

>I have a strange problem in my website. I configured my website to run
under 2 worker processes. (web garden enabled). and I stored my user
information in the current httpcontext(lik e
Httpcontext.cu rrent.items.add ("__currentuser ", myUserobject") and
retrieve the user object like (user =
(UserType)Http context.current .items["__currentu ser"]). the website
authenticati on based on the form authentication. and I used login control
and customized the validation method.

No the bloody problem is. I opened two IE windows. and try to log into
the website using two separate account ([e-mail] and [e-mail]). the login
process is successful, but after that, the two IE windows both display
the information for [e-mail] (instead of one for [e-mail] one for [e-mail]).
Is that anything related with web garden..?

I think the two IE windows should be two separated requests, so that
httpcontexts for two browsers should be different. am I rite?

cheers

[Steven Cheng[MSFT]]

Hi Victor,

As for the HttpContext instance, each coming ASP.NET request will has such
an instance associated with it, and you can refer to many other resource
associate with this request(such as session, request, response .....). And
for the "Items" property, it is a simple Dictionary collection that can
help us transfer some data across each ASP.NET request's server-side
pipeline. For example, you can store some data into Httpcontext.Ite ms in
"BeginReque st" event and retrieve it later in Page's Load event.

As far as I know, no matter whether you're using webgarden or not,
different request's HttpContext.Ite ms should not share the same data(data
in HttpContext.Ite ms should be distroyed after the current request be
processed and ended). Have you set any initial/default value for the
certain HttpContext.Ite ms entry? If convenient, would you post some of the
code snippet on how you store/intialize data into the certain
HttpContext.Ite ms entry and how do you retrieve it and use it(display on
page or ...)? I think there could be something else that cause the Context
items messed.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

=============== =============== =============== =====

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.

[Victor]

Hi Steve:
Thanks for the reply.. my problem is really strange.

my code look like I have this property in my base page.. but i make it as
static.. do you think it's the static make the problem?(make someone
overwrite another person's value)

public static MyUser CurrentUser
{
get
{
if (HttpContext.Cu rrent.Items["__CurrentU ser"] == null)
{
if (HttpContext.Cu rrent.User.Iden tity.Name == "")
return null;

MyUser user =
MyMemberShipPro vider.GetUser(H ttpContext.Curr ent.User.Identi ty.Name, false);
HttpContext.Cur rent.Items.Add( "__CurrentUser" , user);

return user;
}

return (MyUser)HttpCon text.Current.It ems["__CurrentU ser"];
}

set
{
if (HttpContext.Cu rrent.Items.Con tains("__Curren tUser"))
{
HttpContext.Cur rent.Items.Remo ve("__CurrentUs er");
}
HttpContext.Cur rent.Items.Add( "__CurrentUser" , value);
}
}
Another question will be if I store this user object inside the httpcontext,
just as you described, each time a new request initialize, it need to
recreate the user object again(that means access database, recreate the
object) that will increase the server load.I actually do not want to do
that. our website has a quite heavy loading now. So is there anyway I can
store a user object for each user during the period they visit the website
without recreating the user object for every request? Previous I use
thread.GetNamed DataSlot to store the user information. but sometimes it will
lost the information. And I will use Ajax in my website. some people said
that the using thread to store the user info is quite good in the ansync
situation. Can you please give me some information about this.

Cheers
Thank you.




"Steven Cheng[MSFT]" <st*****@online .microsoft.comÐ ´ÈëÏûÏ¢
news:va******** ******@TK2MSFTN GHUB02.phx.gbl. ..

Hi Victor,

As for the HttpContext instance, each coming ASP.NET request will has such
an instance associated with it, and you can refer to many other resource
associate with this request(such as session, request, response .....). And
for the "Items" property, it is a simple Dictionary collection that can
help us transfer some data across each ASP.NET request's server-side
pipeline. For example, you can store some data into Httpcontext.Ite ms in
"BeginReque st" event and retrieve it later in Page's Load event.

As far as I know, no matter whether you're using webgarden or not,
different request's HttpContext.Ite ms should not share the same data(data
in HttpContext.Ite ms should be distroyed after the current request be
processed and ended). Have you set any initial/default value for the
certain HttpContext.Ite ms entry? If convenient, would you post some of
the
code snippet on how you store/intialize data into the certain
HttpContext.Ite ms entry and how do you retrieve it and use it(display on
page or ...)? I think there could be something else that cause the
Context
items messed.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

=============== =============== =============== =====

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Steven Cheng[MSFT]]

Hi Victor,

Glad to hear from you. I don't think the "static" here is incorrect or
wrong here. The problem is possibly due to the HttpContext instances are
pooled(cached) so that a originally instanced HttpContext instance is
reused for multiple requests. You can try print out HttpContext instance's
HashCode to verify this.

However, as I mentioned in previous message, Context.Items collection is
not persisted between multiple page requests. If you want to store data
that will be used among multiple requests of a given client user, I suggest
you use SessionState, and for webfarm/webgarden scenario, you may need to
use SQL Server mode session.

http://idunno.org/articles/277.aspx

Please feel free to post here if you need any further help.

Sincerely,

Steven Cheng
Microsoft MSDN Online Support Lead

[Victor]

Hi Steve.
I managed to print out the hash code of my current httpcontext instances.
everytime i refresh the page, the number is different. so can i assume that
no httpcontext get pooled?

I remove the static. now It looks working fine expect in the tabbed window.
it seems if i open two tabs in the same ie. and login as two different
users.
the last one's user infomation(http context) will override the pervious one.
does that mean the multi tabs in the same ie same the same httpcontext?

Thanks a lot for the help!

Cheers
Victor

"Steven Cheng[MSFT]" <st*****@online .microsoft.comw rote in message
news:nz******** ******@TK2MSFTN GHUB02.phx.gbl. ..

Hi Victor,

Glad to hear from you. I don't think the "static" here is incorrect or
wrong here. The problem is possibly due to the HttpContext instances are
pooled(cached) so that a originally instanced HttpContext instance is
reused for multiple requests. You can try print out HttpContext instance's
HashCode to verify this.

However, as I mentioned in previous message, Context.Items collection is
not persisted between multiple page requests. If you want to store data
that will be used among multiple requests of a given client user, I
suggest
you use SessionState, and for webfarm/webgarden scenario, you may need to
use SQL Server mode session.

http://idunno.org/articles/277.aspx

Please feel free to post here if you need any further help.

Sincerely,

Steven Cheng
Microsoft MSDN Online Support Lead

[Steven Cheng[MSFT]]

Thanks for your reply Victor,

For HttpContext instance, it does be separated for each client request,
actually, each ASP.NET request will be processed under a separate
HttpApplication instance. Here is a kb article describe this:

#INFO: Application Instances, Application Events, and Application State in
ASP.NET
http://support.microsoft.com/kb/312607

For the following problem you mentioned:

=============== =============== ==========
it seems if i open two tabs in the same ie. and login as two different
users. the last one's user infomation(http context) will override the
pervious one.
does that mean the multi tabs in the same ie same the same httpcontext?
=============== =============== =========

Are you using SessionState to store some information that will be displayed
to user? For client browser(IE), if you use "tab" or "file-->new window" to
open a new browser, it will share the same session with original browser.
Only if you start a separate IE instance from program menu or shotcut will
it start a new session.

Also, as you mentioned that you'll need to display separate information for
each forms authenticated user, correct? If so, I think you can consider
using the "Profile" properties to store data that need to be separated for
each forms authenticated user. SessionState is not completely 1:1 mapping
to forms authentifcated user. Here are some reference about ASP.NET 2.0
profile properties:

#ASP.NET Profile Properties Overview
http://msdn2.microsoft.com/en-us/lib...xs(VS.80).aspx

#Profiles In ASP.NET 2.0
http://www.odetocode.com/Articles/440.aspx

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

[Victor]

Hi Steve:
Thanks so much for the help.

for my problem.

=============== =============== ==========
it seems if i open two tabs in the same ie. and login as two different
users. the last one's user infomation(http context) will override the
pervious one.
does that mean the multi tabs in the same ie same the same httpcontext?
=============== =============== =========

I didn't use seesionstate to store my user infomation now. What I did is
when each request began, I create a user object from db then store them into
the httpcontext.cur rent.items collection. then it can be used across the
current request. This issue almost killed me......@_@

thanks a lot.

Victor

"Steven Cheng[MSFT]" <st*****@online .microsoft.comw rote in message
news:ek******** ******@TK2MSFTN GHUB02.phx.gbl. ..

Thanks for your reply Victor,

For HttpContext instance, it does be separated for each client request,
actually, each ASP.NET request will be processed under a separate
HttpApplication instance. Here is a kb article describe this:

#INFO: Application Instances, Application Events, and Application State in
ASP.NET
http://support.microsoft.com/kb/312607

For the following problem you mentioned:

=============== =============== ==========
it seems if i open two tabs in the same ie. and login as two different
users. the last one's user infomation(http context) will override the
pervious one.
does that mean the multi tabs in the same ie same the same httpcontext?
=============== =============== =========

Are you using SessionState to store some information that will be
displayed
to user? For client browser(IE), if you use "tab" or "file-->new window"
to
open a new browser, it will share the same session with original browser.
Only if you start a separate IE instance from program menu or shotcut will
it start a new session.

Also, as you mentioned that you'll need to display separate information
for
each forms authenticated user, correct? If so, I think you can consider
using the "Profile" properties to store data that need to be separated for
each forms authenticated user. SessionState is not completely 1:1 mapping
to forms authentifcated user. Here are some reference about ASP.NET 2.0
profile properties:

#ASP.NET Profile Properties Overview
http://msdn2.microsoft.com/en-us/lib...xs(VS.80).aspx

#Profiles In ASP.NET 2.0
http://www.odetocode.com/Articles/440.aspx

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no
rights.

[Steven Cheng[MSFT]]

Hi Victor,

Thanks for your reply.

That does be a bit strange. I'd like to help perform some test on my side.
would you try creating a simplified web project(with the least page and
code ) that can repro the behavior? You can send it to me through email(my
email is in my signature , remove the "online" in it).

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.