Tfs 2017 Update 2 - “WorkItem 用户交付"工作卡住 - 没有电子邮件/肥皂通知 [英] Tfs 2017 Update 2 - "WorkItem user delivery" job stuck - no email/soap notifications

问题描述

我有一份工作WorkItem User Delivery"，似乎卡在 TFS 2017 Update 2 (SQL Server 2016) 中.它已经运行了 4 天，并导致其他邮件/soap 作业出现问题，并且电子邮件警报非常零星:TFS OI 中的 JobQueue 图像

I have a job "WorkItem User Delivery" that seems to be stuck in TFS 2017 Update 2 (SQL Server 2016). It's been running for 4 days and is causing issues with the other mail/soap jobs and email alerts are very sporadic: Image of JobQueue in TFS OI

我在 [Tfs_Configuration].[dbo].[tbl_JobQueue] 中找到了 JobID 为 631F49B3-46E1-42EC-8FFF-081BD176C18A 的作业.我已经重新启动了 TFSJobAgent 没有运气.从表中删除这一行是否安全，这对删除作业是否有效?

I've located the job in [Tfs_Configuration].[dbo].[tbl_JobQueue] with a JobID of 631F49B3-46E1-42EC-8FFF-081BD176C18A. I've already restarted TFSJobAgent with no luck. Is it safe to delete this row from the table and will that be effective in removing the job?

推荐答案

我们最近在我们的生产基础设施中添加了两个新的应用程序层，因为我们准备迁移到一个新的本地数据中心.这两个新的应用程序层没有添加到我们的负载平衡 VIP 中，因此实际上没有负载到达它们(除非我直接点击它们).

We recently added two new application tiers to our production infrastructure as we get ready to migrate to a new On-Premises data center. These two new application tiers were not added to our load balanced VIP so no load was actually getting to them (except when I hit them directly).

这些新机器没有防火墙访问当前 prod 数据中心正在侦听 SOAP 调用的机器(甚至可能没有到邮件主机).我相信 TFS 将这些通知/soap 作业卸载到其中一台新机器上，因为一旦我在所有四台机器上关闭 TFSJobAgent 并在只有两台原始机器上重新打开它时，一切都会重新开始工作.

These new machines didn't have firewall access to the machine that is listening for SOAP calls in the current prod data center (and possibly not even to the mailhost). I believe TFS offloaded these notification/soap jobs to one of these new machines because as soon as I turned off TFSJobAgent on all four machines and turned it back on on only the two original machines did everything start working again.

这篇关于Tfs 2017 Update 2 - “WorkItem 用户交付"工作卡住 - 没有电子邮件/肥皂通知的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！