Azure的辅助角色与回收未处理服务总线故障信息 [英] Azure worker role recycling with unhandled Service Bus fault message
问题描述
我一直在运行使用Microsoft.ServiceBus 2.2库从其他辅助角色和Web角色发布的工作回应了Azure的工人角色部署。最近（周围可疑讨论的OS更新时间<一个href=\"http://weblogs.asp.net/scottgu/archive/2013/10/18/windows-azure-announcing-support-for-windows-server-2012-r2-some-nice-price-cuts.aspx\"相对=nofollow>这里），群集的实例不断地开始回收，重新启动，运行的时间很短，然后再次循环。
I have been running an Azure worker role deployment that uses the Microsoft.ServiceBus 2.2 library to respond to jobs posted from other worker roles and web roles. Recently (suspiciously around the time of the OS update discussed here), the instances of the cluster started constantly recycling, rebooting, running for a short period of time, and then recycling again.
我可以证实，角色实例使其一路过关斩将从跟踪消息我在我的诊断我RoleEntryPoint的的OnStart（）方法。偶尔，Azure管理门户的实例窗格中会提到一个循环角色经历了一个未处理的异常，但不会给更多的细节。用远程桌面登录到其中一个实例后，两条线索我是：
I can confirm that the role instances make it all the way through the OnStart() method of my RoleEntryPoint from the trace messages I have in my diagnostics. Occasionally, the Instances pane of the Azure Management Portal would mention that a recycling role had experienced an "unhandled exception," but would not give more detail. After logging in with remote desktop to one of the instances, the two clues I have are:
- 的性能计数器表明\\处理器（_Total）\\％处理器时间徘徊在100％，周期性下降到80年代中期，在\\ TCPv4滴\\已建立的连接恰逢。在\\ TCPv4一些滴\\建立不与\\处理器（_Total）\\％处理器时间下降相关连接。
-
我能找到，在其中一个实例的服务器管理本地服务器事件，以下消息：
- Performance counters indicate that \Processor(_Total)\% Processor Time is hovering at 100%, periodically dropping to the mid-80s coinciding with drops in \TCPv4\Connections Established. Some drops in \TCPv4\Connections Established do not correlate with drops in \Processor(_Total)\% Processor Time.
I was able to find, in the Local Server Events in the Server Manager of one of the instances, the following message:
应用：WaWorkerHost.exe
Framework版本：v4.0.30319
说明：该过程由于未处理的异常终止。
异常信息：Microsoft.ServiceBus.Common.CallbackException
堆栈：
在Microsoft.ServiceBus.Common.Fx + IOCompletionThunk.UnhandledExceptionFrame（UInt32的，UInt32的，System.Threading.NativeOverlapped *）
在System.Threading._IOCompletionCallback.PerformIOCompletionCallback（UInt32的，UInt32的，System.Threading.NativeOverlapped *）
Application: WaWorkerHost.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: Microsoft.ServiceBus.Common.CallbackException Stack: at Microsoft.ServiceBus.Common.Fx+IOCompletionThunk.UnhandledExceptionFrame(UInt32, UInt32, System.Threading.NativeOverlapped*) at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
有已经在此期间与该服务相关的公交车没有权限的配置变化，出现此消息，尽管我们没有任何更新，我们的虚拟机。尽管如此，也出现了我们的服务仍在运行=>工作正在处理中，并从他们正在收听的服务总线队列中删除。
There have been no permissions configuration changes associated with the service bus during this time, and this message occurs despite us not having updated any of our VMs. Nonetheless, it also appears that our service is still functioning => jobs are being processed and removed from the Service Bus Queues they are listening to.
大多数谷歌搜索在这些问题上轮番上涨的建议，这是某种联系的IntelliTrace，但是，这些虚拟机没有同时开启的IntelliTrace。
Most Googling on these issues turns up suggestions that this is somehow related to IntelliTrace, however, these VMs do not have IntelliTrace enabled on them.
有没有人有什么是怎么回事任何想法？
Does anyone have any ideas on what is going on here?
推荐答案
我有类似的问题。主要的原因是，它无法解析服务总线DLL版本问题，确保在AppSettings的重定向版本和您的版本实际添加参照相同。
它可以与任何DLL不匹配发生不仅与服务总线的dll ...
I had the similar issue. The main reason is that it could not resolve the Service Bus dll version issues make sure the version you are redirecting in AppSettings and the version you actually added reference to are same. It may occur with any dll mismatches not only with service bus dll...
这篇关于Azure的辅助角色与回收未处理服务总线故障信息的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
