NServiceBus Send-Only 端点不生成心跳

NServiceBus Send-Only endpoints not generating heartbeats

我正在使用 NServiceBus.Core v6.4.3NServiceBus.Heartbeat v2.0.0

我有一个控制台应用程序 运行 作为计划任务,它提取数据并将命令发送到端点进行处理。

控制台应用程序配置为 SendOnly 端点。

我的代码如下:

主要

// Local NServiceBus Configuration
var endpointConfiguration = EndpointConfiguration();
// Global NServiceBus & Ninject configuration
var conventions = new NServiceBusConventions();
conventions.Customize(endpointConfiguration);
// Create and start endpoint
var endpointInstance = await Endpoint.Start(endpointConfiguration).ConfigureAwait(false);

端点配置

private static EndpointConfiguration EndpointConfiguration()
{
    var configuration = new EndpointConfiguration("EndpointName");

    // To ensure OctopusDeploy doesn't cause ServicePulse to think multiple services have been deployed
    // http://docs.particular.net/nservicebus/hosting/override-hostid
    configuration.UniquelyIdentifyRunningInstance()
        .UsingNames("EndpointName", Environment.MachineName);

    configuration.SendOnly();

    return configuration;         
}

约定

public class NServiceBusConventions
{
    public IKernel Kernel;

    public void Customize(EndpointConfiguration configuration)
    {
        // Custom Logging Factory implementation
        LogManager.UseFactory(new NServiceBusTraceLoggerFactory());

        Kernel = NinjectCommon.Start();

        configuration.UseContainer<NinjectBuilder>(b => b.ExistingKernel(Kernel));
        configuration.UsePersistence<NHibernatePersistence>();
        configuration.UseSerialization<JsonSerializer>();
        configuration.UseTransport<MsmqTransport>();
        var transport = configuration.UseTransport<MsmqTransport>();
        // Enabled by default in MsmqTransport, but to ensure we have it
        transport.Transactions(TransportTransactionMode.TransactionScope);

        configuration.DefineCriticalErrorAction(NServiceBusOnCriticalError.OnCriticalError);    

        configuration.EnableInstallers();
        configuration.Conventions()
            .DefiningCommandsAs(t => t.Namespace != null && t.Namespace.Equals("Contracts.Commands"))
            .DefiningEventsAs(t => t.Namespace != null && t.Namespace.Equals("Contracts.Interfaces.Events"));

        configuration.AuditProcessedMessagesTo(ConfigurationManager.AppSettings["Messaging.NServiceBus.QueueNames.AuditQueue"]);
        configuration.SendFailedMessagesTo(ConfigurationManager.AppSettings["Messaging.NServiceBus.QueueNames.ErrorQueue"]);
        configuration.SendHeartbeatTo(ConfigurationManager.AppSettings["Messaging.NServiceBus.QueueNames.ServiceControlQueue"]);

        var scanner = configuration.AssemblyScanner();

        var excludeRegexs = new List<string>
        {
            @"DevExpress.*\.dll"
        };

        var baseDirectory = AppDomain.CurrentDomain.BaseDirectory;
        foreach (var fileName in Directory.EnumerateFiles(baseDirectory, "*.dll").Select(Path.GetFileName))
        {
            foreach (var pattern in excludeRegexs)
            {
                if (Regex.IsMatch(fileName, pattern, RegexOptions.IgnoreCase))
                {
                    scanner.ExcludeAssemblies(fileName);
                    break;
                }
            }
        }
    }
}

删除 EndpointConfiguration 中的 configuration.SendOnly(); 行会使端点出现在 ServicePulse 中,但不会出现在其他地方。

我知道这是以前版本中的问题,但我认为这已在 NServiceBus V5 中修复。

我不必将端点配置为仅发送,但我只是为了完整起见。

心跳丢失的原因是:

I have a console application running as a Scheduled Task, it extracts data and send commands to an endpoint for processing.

进程每次都会重新开始,提取数据、处理和发送命令所花费的时间对于 NServiceBus 来说太短,无法发送心跳消息。

在应用程序末尾放置一个 await Task.Delay(10000) 足以让 NServiceBus 完成其必要的引导,并且不会影响我们的 SLA。

感谢 Sean Farmar 帮助诊断