NServiceBus工作人员检查容量为0

时间:2015-05-07 17:30:03

标签: msmq nservicebus

我正在使用NServiceBus 3.3。我正在尝试新的Pre-Prod-Environment设置。

这一切在我的现有配置中的生产和我现有的Pre-Prod-Environments中都能正常工作。

但是在我的新环境中,我正在让我的工作人员以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>

1 个答案:

答案 0 :(得分:1)

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