我们如何使用LightSwitch管理空闲的超时值? [英] How do we manage idle Timeout Value with LightSwitch?

问题描述

我正在测试来自以下客户的带有SL  Clients (使用Forms Auth)的LS应用程序的迁移:

I am testing the migration of our LS apps with SL Clients (using Forms Auth) from:

• Windows Server 2008 R2，SQL Server 2008 R2和VS 2012 Upd 1

收件人:

• Windows Server 2012，SQL Server 2012和VS 2012 Upd 2

我们的托管环境是完整的Hyper-V VM. 2008年和2012年的VM都来自同一家公司.

Our hosting environment is full Hyper-V VMs.   Both the 2008 and 2012 VMs are from the same company.

但是，我发现2012/Upd2环境有时仅在几分钟后就使数据库访问超时.

However, I am finding that the 2012/Upd2 environment is timing out the database access sometimes after only a few minutes.

据我所知，我已经复制了所有的配置和应用程序代码.

As far as I know, I've replicated all of the config and application code the same.

下面是应用程序请求的屏幕截图，该请求使用户再次输入其aspnet凭据.

Here's a screenshot of the app request to have the user enter their aspnet credentials again.

有人知道造成这种情况的原因吗?

Does anyone have an idea what might be causing this.

如果我输入我的aspnet登录名/密码，则该应用程序将不会接受它.尝试三次失败后，必须重新设置用户密码.

If I enter my aspnet login/password, the app will not accept it.   After three failed attempts, the user password will have to be reset.

如果用户的网络连接长时间中断和/或在4个小时内未使用他们的应用程序，则用户当前会遇到此弹出式重新登录屏幕.我试图找出原因，新的2012/Upd2环境无法正常工作 与2008/Upd1环境相同.在这两种环境下，其他所有功能都运行良好.

Users currently experience this pop-up re-login screen, if they have a prolonged break in their network connection and/or have not used their application within 4 hours.  I'm trying to figure out why the new 2012/Upd2 environment is not working the same as the 2008/Upd1 environment.   Everything else is working wonderfully well in both environments.

有想法吗?

Garth Henderson-先锋商务技术

Garth Henderson - Vanguard Business Technology

推荐答案

IIS应用程序池设置为可以存活4小时:

The IIS App Pool is set to stay alive for 4 hours:

但是，即使我重新输入了正确的aspnet凭据，后续更新也会崩溃:

However, even after I re-enter the correct aspnet credentials, subsequent updates crash:

当然，我的应用程序代码中没有错误.该代码已经在生产环境中运行了一年多.如果我仅重新登录，代码就可以正常工作.

Of course, there is no error in my application code.   This code has been running in production for over a year.   If I simply log back in, the code works fine.

使用Web服务后端的LS的较低内部结构发生了某些事情.客户端View似乎工作正常，但是JSON OData Web服务(JOWS)不能正常工作.

Something has happened with the lower level internals of LS with the web services backend.   It seems that the client View is working OK, but the JSON OData Web Services (JOWS) is not working as it should. 

这些应用程序仅使用2个外部数据SQL数据源-没有内部数据库，没有RIA，没有Azure，没有SharePoint.

The apps are just using 2 External Data SQL Data Sources - no internal DB, no RIA, no Azure, no SharePoint.

这篇关于我们如何使用LightSwitch管理空闲的超时值?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！