为什么我的实例同一地点的Azure缓存尝试存储会话时回收? [英] Why do my instances recycle when trying to store sessions in co-located Azure cache?
问题描述
我运行一个ASP.Net MVC3应用程序,并遵循的此Windows Azure的操作方法的如何我会存储在Windows Azure中的同一位置的缓存。
I run an ASP.Net MVC3 application and have followed this Windows Azure How-To on how to store my sessions in a co-located cache in Windows Azure.
我已经安装了提到的NuGet包,并应用了必要的信息,我的web.config。该网站的作用是设置运行2小的情况下,并用30%的共设缓存。
I have installed the mentioned Nuget-package, and applied the necessary information to my web.config. The web role is setup to run 2 small instances, and use a 30% co-located cache.
当我部署到Azure中,我只是实例回收。通过远程桌面连接到其中一个实例,我发现在日志中这两个事件,似乎相关的:
When I deploy to Azure, my instances just recycle. Through a remote desktop connection to one of the instances, I have found these two events in the logs, that seem related:
该CacheStatusIndicator服务意外终止。它已完成
这1时间(s)。下面的纠正措施将在1000采取
毫秒:重新启动服务
The CacheStatusIndicator service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service.
该CacheService服务意外终止。它已完成此1
时间(s)。以下的修正操作将在60000采取
毫秒:重新启动服务
The CacheService service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
不过,我找不到上的信息。
However, I cannot find much information on that.
有没有人有什么线索我可能会丢失在这里吗?
Does anyone have a clue what I might be missing here?
推荐答案
现在我用我的共享的时间来处理这个数额,最后它似乎是工作。不知道到底是什么部分解决了这个问题,但我会包我所做的更改,万一别人有同样的问题在某些时候。
Now I spent my shared amount of time dealing with this, and finally it seems to be working. Not sure exactly what part solved the problem, but I'll wrap up the changes I made, in case someone else have the same issue at some point.
- 在调试这个问题,我也更新了我从MVC3到MVC4应用。不知道这有什么关系解决这个问题,但至少它是我做出的改变之一。
- 我注意到另一个异常是由该服务的IntelliTrace抛出,所以我禁用,在部署和重新部署的应用程序(我的猜测是,这是什么问题造成的实际实例循环。
从Microsoft支持在这个问题上响应:
我排除这个问题的部署和我从CacheService.exe
I was troubleshooting your deployment with the issue and I got a memory dump from the CacheService.exe
这是被抛出的异常
CLR异常类型:System.TypeInitializationException
对于'Microsoft.ApplicationServer.Caching.AzureCommon.AzureUtility'的类型初始扔
一个例外ModLoad:000007fe ea010000 000007fe
ea0fa000结果
D:\\ WINDOWS \\ Microsoft.NET \\ Framework64 \\ v4.0.30319 \\ diasymreader.dll
的 * 的错误:符号文件找不到。默认输出符号D:\\ WINDOWS \\ SYSTEM32 \\ KERNEL32.dll中 -
NTDLL ZwWaitForMultipleObjects +是0xA:00000000`76f5739a C3结果
RET
CLR exception type: System.TypeInitializationException "The type initializer for 'Microsoft.ApplicationServer.Caching.AzureCommon.AzureUtility' threw an exception." ModLoad: 000007fe
ea010000 000007fe
ea0fa000
D:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll * ERROR: Symbol file could not be found. Defaulted to export symbols for D:\windows\system32\KERNEL32.dll - ntdll!ZwWaitForMultipleObjects+0xa: 00000000`76f5739a c3
ret
在此命名空间中的例外可能发生,如果:
The exceptions on this namespace can happen if:
- 您设置
Microsoft.WindowsAzure.Plugins.Caching.ConfigStoreConnectionString
设置上ServiceConfiguration使用本地存储模拟器 - 在你有
&LT的标识值在web.config; dataCacheClients>
部分未设置为正确的角色名称 - 在某些罕见的情况下,如果你有1.6和1.7一起安装SDK这可能会导致一些混淆DLL时项目正在建设中。
- You set the
Microsoft.WindowsAzure.Plugins.Caching.ConfigStoreConnectionString
setting on ServiceConfiguration to use the local storage emulator - On the web.config you have the identifier value of the
<dataCacheClients>
section not set to the correct role name - In some rare cases if you have the SDK 1.6 and 1.7 installed together this can cause some mixed up DLLs when project is being built.
这篇关于为什么我的实例同一地点的Azure缓存尝试存储会话时回收?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!