容量为 0 的 NServiceBus Worker 签入

NServiceBus Worker checking in with capacity of 0

我正在使用 NServiceBus 3.3。我正在尝试获得新的预生产环境设置。

它在生产中以及在我现有的预生产环境之一和我现有的配置中都运行良好。

但是在我的新环境中,我让我的工作人员以 0 的容量签到。(他们在工作环境中以 1 的容量签到)。

同样,环境之间的配置相同。(当然除了机器名称。)

知道为什么会发生这种情况吗?

这是我的日志输出(更改了队列名称和机器名称):

2015-05-07 10:53:33,904 [1] INFO  NServiceBus.Host [(null)]  - Going to activate profile: NServiceBus.Distributor, NServiceBus.Host, Version=3.3.0.0, Culture=neutral, PublicKeyToken=9fc386479f8a226c
2015-05-07 10:53:33,904 [1] INFO  NServiceBus.Host [(null)]  - Going to activate profile: NServiceBus.Production, NServiceBus.Host, Version=3.3.0.0, Culture=neutral, PublicKeyToken=9fc386479f8a226c
2015-05-07 10:53:33,919 [1] INFO  NServiceBus.Host [(null)]  - Going to activate profile: NServiceBus.PerformanceCounters, NServiceBus.Host, Version=3.3.0.0, Culture=neutral, PublicKeyToken=9fc386479f8a226c
2015-05-07 10:53:33,935 [1] WARN  Distributor.myFromQueue [(null)]  - No transport configuration found so the distributor will default to one thread, for production scenarios you would want to adjust this setting
2015-05-07 10:53:33,950 [1] INFO  Distributor.myFromQueue [(null)]  - Endpoint configured to host the distributor, applicative input queue re routed to myFromQueue.worker@DistributorHost
2015-05-07 11:10:05,015 [Worker.13] INFO  Distributor.myFromQueue [(null)]  - Worker myFromQueue@WorkerMachine has started up, clearing previous reported capacity
2015-05-07 11:10:05,030 [Worker.13] INFO  Distributor.myFromQueue [(null)]  - Worker myFromQueue@WorkerMachine checked in with available capacity: 0

这是我的工作人员配置文件的相关部分:

  <MsmqTransportConfig NumberOfWorkerThreads="4" MaxRetries="5" />
  <MessageForwardingInCaseOfFaultConfig ErrorQueue="error" />
  <MasterNodeConfig Node="DistributorHost" />
  <UnicastBusConfig>
    <MessageEndpointMappings>
      <add Messages="Bus.MyMessageAssembly" Endpoint="QueueForTheDistributor@DistributorHost" />
    </MessageEndpointMappings>
  </UnicastBusConfig>

我遇到了同样的问题,并且能够通过删除工作代理上的队列(myfromqueue 和 myfromqueue.retries)来解决它。 NServiceBus 自动重新创建了队列,一切都重新开始为我处理。