ASP.NET 2.0 - 丢失会话信息 [英] ASP.NET 2.0 - Loosing session information

查看:64
本文介绍了ASP.NET 2.0 - 丢失会话信息的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

大家好:


我在IIS 6.0下运行.NET 2.0上的Web应用程序和

的用户这个应用程序似乎正在失去他们的会话随机 - 我们没有

能够识别任何模式,除了事件中的警告

查看器说一个服务应用程序池xyz终止的进程

意外。


..NET 1.1也安装在同一台机器上 - 2.0和1.1应用程序有单独的

应用程序池。


我已从IIS中的应用程序池中删除了默认的回收检查

,以便工作进程永远不会自动回收。用于Web应用程序的

web.config使用inProc会话模式,相关的

键是:


< sessionState mode = QUOT;是InProc" stateNetworkTimeout =""

stateConnectionString =" tcpip = 127.0.0.1:42424" sqlConnectionString =" data

source = 127.0.0.1; user id = sa; password =" cookieless =" false"

timeout =" 65" />


此行为在我们从
迁移同一个Web应用程序后启动
1.1到2.0。


感谢您提前的帮助,

Cyndi

Hi Everyone:

I have a web application running on .NET 2.0 under IIS 6.0 and users of
this application seem to be loosing their session randomly - we havent
been able to identify any pattern, except for warnings in the event
viewer that say "A process serving application pool xyz terminated
unexpectedly."

..NET 1.1 is also installed on the same machine -- there are separate
app pools for 2.0 and 1.1 apps.

I have removed the default recycling checks from the app pools in IIS
so that the worker process is never recycled automatically. The
web.config for the web app uses inProc session mode and the relevant
key is:

<sessionState mode="InProc" stateNetworkTimeout=""
stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data
source=127.0.0.1;user id=sa;password=" cookieless="false"
timeout="65"/>

This behavior started after we migrated the same web application from
1.1 to 2.0.

Thanks for your help in advance,
Cyndi

推荐答案

您是否考虑将sessionState模式从InProc更改为
到StateServer或SQLServer?


如果ASP.NET工作进程循环使用,而你的sessionState模式

正在进行中运行(Inproc),你的会话变量将会丢失。


如果ASP .NET工作进程回收,你的sessionState模式

正在运行进程外(无论是StateServer还是SQLServer),

您的会话变量不会丢失。 />


Juan T. Llibre,asp.net MVP

aspnetfaq.com: http://www.aspnetfaq.com/

asp.net f aq: http://asp.net.do/faq/

foros de asp.net,en espa?ol: http:// asp .net.do / foros /

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

< cy ********* @ yahoo.com>在留言中写道

news:11 ********************** @ u72g2000cwu.googlegr oups.com ...
Have you considered changing your sessionState mode from "InProc"
to StateServer or SQLServer ?

If the ASP.NET worker process recycles, and your sessionState mode
is running in-process (Inproc), your session variables will be lost.

If the ASP.NET worker process recycles, and your sessionState mode
is running out-of-process (whether StateServer or SQLServer),
your session variables will not be lost.


Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espa?ol : http://asp.net.do/foros/
===================================
<cy*********@yahoo.com> wrote in message
news:11**********************@u72g2000cwu.googlegr oups.com...
大家好:

我有一个在IIS 6.0下运行在.NET 2.0上的Web应用程序,而且这个应用程序的用户似乎随机丢失了他们的会话 - 我们没有
能够识别任何模式,但事件
查看器中的警告说出现服务应用程序池xyz的进程意外终止。

.NET 1.1是也安装在同一台机器上 - 有2.0和1.1应用程序的单独的应用程序池。

我已从IIS中的应用程序池中删除了默认的回收检查
工作进程永远不会自动回收。 Web应用程序的web.config使用inProc会话模式,相关的关键是:

< sessionState mode =" InProc" stateNetworkTimeout =""
stateConnectionString =" tcpip = 127.0.0.1:42424" sqlConnectionString =" data
source = 127.0.0.1; user id = sa; password =" cookieless =" false"
timeout =" 65" />

此行为是在我们将同一个Web应用程序从
1.1迁移到2.0之后开始的。

感谢您提前的帮助,
Cyndi
Hi Everyone:

I have a web application running on .NET 2.0 under IIS 6.0 and users of
this application seem to be loosing their session randomly - we havent
been able to identify any pattern, except for warnings in the event
viewer that say "A process serving application pool xyz terminated
unexpectedly."

.NET 1.1 is also installed on the same machine -- there are separate
app pools for 2.0 and 1.1 apps.

I have removed the default recycling checks from the app pools in IIS
so that the worker process is never recycled automatically. The
web.config for the web app uses inProc session mode and the relevant
key is:

<sessionState mode="InProc" stateNetworkTimeout=""
stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data
source=127.0.0.1;user id=sa;password=" cookieless="false"
timeout="65"/>

This behavior started after we migrated the same web application from
1.1 to 2.0.

Thanks for your help in advance,
Cyndi



嗨Juan,


感谢您的回复 - 我们可以考虑转移到其他sessionState

模式,但我担心为什么我们突然遇到问题

inProc模式。


有人在将现有的

1.1网络应用迁移到2.0后遇到过​​这个问题吗?


谢谢,

Cyndi

Hi Juan,

Thanks for your reply - we could consider moving to other sessionState
modes but I''m concerned as to why we are suddenly having issues with
inProc mode.

Has someone came across this issue after they migrated their existing
1.1 web apps to 2.0?

Thanks,
Cyndi


2006年4月1日17:10:35 -0800, cy ********* @ yahoo.com 写道:
On 1 Apr 2006 17:10:35 -0800, cy*********@yahoo.com wrote:
嗨娟,

感谢您的回复 - 我们可以考虑转移到其他sessionState
模式,但我担心为什么我们突然遇到问题
inPro c模式。

有人在将现有的
1.1网络应用迁移到2.0之后遇到过这个问题吗?
Hi Juan,

Thanks for your reply - we could consider moving to other sessionState
modes but I''m concerned as to why we are suddenly having issues with
inProc mode.

Has someone came across this issue after they migrated their existing
1.1 web apps to 2.0?




转到因为这是一个糟糕的主意,因此这是一个糟糕的主意。

您在事件查看器中看到的内容表明您遇到了崩溃。

遇到了崩溃。您需要找出崩溃发生的原因。

您能否发布您所看到的此活动的详细信息?


最佳方式解决这样的问题是获取用户模式

崩溃转储并使用Windbg或其他此类调试器来确定

导致它。

Jim



Moving to out-of-proc Session state because of this is a bad idea.
What you''re seeing in the Event Viewer indicates that you are
experiencing a crash. You need to find out why the crash is occurring.

Can you post the details of this event you are seeing?

The best way to troubleshoot something like this is to get a user-mode
crash dump and use Windbg or another such debugger to determine what
caused it.

Jim


这篇关于ASP.NET 2.0 - 丢失会话信息的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆