NServiceBus Saga没有注册IPersistTimeouts组件

时间：2015-11-02 09:22:27

标签： c# scheduled-tasks saga nservicebus5

我有一个自我加密的WCF主机（IIS），我在NServiceBus配置期间遇到此异常：

  

抛出异常：NServiceBus.Core.dll中的'Autofac.Core.Registration.ComponentNotRegisteredException'

     

其他信息：请求的服务'NServiceBus.Timeout.Core.IPersistTimeouts'尚未注册。要避免此异常，请注册组件以提供服务，使用IsRegistered（）检查服务注册，或使用ResolveOptional（）方法解析可选依赖项。

我正在使用带有内存持久性和 MSMQ传输的NSB 5.2.9。

这是我对自托管WCF主机（IIS）的配置。 没有App.config！ **这是在global.asax中的Autofac注册后调用的： 

    public static void CreateSelfHost( string endpointName, ILifetimeScope container )
    {
        if ( Bus != null )
            return;

        lock ( syncLock )
        {
            var config = new BusConfiguration();

            config.UseContainer<AutofacBuilder>( c => c.ExistingLifetimeScope( container ) );

            var includesBuilder = AllAssemblies.Matching( "Company.App." );
            config.AssembliesToScan( includesBuilder );

            config.UseSerialization<JsonSerializer>();
            config.UseTransport<MsmqTransport>();
            config.UsePersistence<InMemoryPersistence>();
            config.DisableFeature<SecondLevelRetries>();    //turn off for in-mem persistence, otherwise could lose messages
            config.EndpointName( endpointName );


            config.EnableInstallers(); //ensures msmq is created
            config.PurgeOnStartup( true ); //only for self-hosted

            config.Transactions().Disable();
            config.DisableFeature<StorageDrivenPublishing>();

            Bus = NServiceBus.Bus.CreateSendOnly( config ); //create SendOnlyBus here
        }
    }

所有端点上的配置仅通过IProvideConfiguration<>完成。

在项目的属性中设置了 NServiceBus.Lite 个人资料，但没有区别。

我是NSB的新手，我无法解释为什么会这样。 我一直在寻找能够说IPersistsTimeouts的方法，但我找到的任何方法都被标记为过时且不起作用。

编辑＃1： @DavidBoike

要求的功能转储 
------------- FEATURES ----------------
Name: CriticalErrorHandling
Version: 5.2.9
Enabled by Default: Yes
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: CustomIDataBus
Version: 5.2.9
Enabled by Default: No
Status: Disabled
Deactivation reason: Did not meet one of the dependencies: [DataBus]
Name: DataBus
Version: 5.2.9
Enabled by Default: Yes
Status: Disabled
Deactivation reason: Did not fulfill its Prerequisites:
   -No databus properties was found in available messages
Name: Encryptor
Version: 5.2.9
Enabled by Default: Yes
Status: Disabled
Deactivation reason: Did not fulfill its Prerequisites:
   -No encryption properties was found in available messages
Name: ErrorSubscribers
Version: 5.2.9
Enabled by Default: Yes
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: ForwarderFaultManager
Version: 5.2.9
Enabled by Default: Yes
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: InMemoryFaultManager
Version: 5.2.9
Enabled by Default: No
Status: Disabled
Deactivation reason: Did not meet one of the dependencies: 
Name: InstallationSupport
Version: 5.2.9
Enabled by Default: Yes
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: CriticalTimeMonitoring
Version: 5.2.9
Enabled by Default: No
Status: Disabled
Deactivation reason: Did not meet one of the dependencies: 
Name: Audit
Version: 5.2.9
Enabled by Default: Yes
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: AutoSubscribe
Version: 5.2.9
Enabled by Default: Yes
Status: Enabled
Dependencies: None
Startup Tasks: ApplySubscriptions
Name: MsmqSubscriptionPersistence
Version: 5.2.9
Enabled by Default: No
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: Scheduler
Version: 5.2.9
Enabled by Default: Yes
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: CustomSerialization
Version: 5.2.9
Enabled by Default: Yes
Status: Disabled
Deactivation reason: Did not fulfill its Prerequisites:
   -CustomSerialization not enable since serialization definition not detected.
Name: ForwardReceivedMessages
Version: 5.2.9
Enabled by Default: Yes
Status: Disabled
Deactivation reason: Did not fulfill its Prerequisites:
   -No forwarding address was defined in the unicastbus config
Name: RegisterHandlersInOrder
Version: 5.2.9
Enabled by Default: Yes
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: SLAMonitoring
Version: 5.2.9
Enabled by Default: No
Status: Disabled
Deactivation reason: Did not meet one of the dependencies: 
Name: LicenseReminder
Version: 5.2.9
Enabled by Default: Yes
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: Outbox
Version: 5.2.9
Enabled by Default: No
Status: Disabled
Deactivation reason: Did not meet one of the dependencies: 
Name: InMemoryGatewayPersistence
Version: 5.2.9
Enabled by Default: No
Status: Disabled
Deactivation reason: Did not meet one of the dependencies: [Gateway]
Name: InMemoryOutboxPersistence
Version: 5.2.9
Enabled by Default: No
Status: Disabled
Deactivation reason: Did not meet one of the dependencies: [Outbox]
Name: InMemorySagaPersistence
Version: 5.2.9
Enabled by Default: No
Status: Disabled
Deactivation reason: Did not meet one of the dependencies: [Sagas]
Name: InMemorySubscriptionPersistence
Version: 5.2.9
Enabled by Default: No
Status: Disabled
Deactivation reason: Did not meet one of the dependencies: [MessageDrivenSubscriptions]
Name: InMemoryTimeoutPersistence
Version: 5.2.9
Enabled by Default: No
Status: Disabled
Deactivation reason: Did not meet one of the dependencies: [TimeoutManager]
Name: TimeoutManagerBasedDeferral
Version: 5.2.9
Enabled by Default: No
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: UnicastBus
Version: 5.2.9
Enabled by Default: Yes
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: BinarySerialization
Version: 5.2.9
Enabled by Default: Yes
Status: Disabled
Deactivation reason: Did not fulfill its Prerequisites:
   -BinarySerialization not enable since serialization definition not detected.
Name: BsonSerialization
Version: 5.2.9
Enabled by Default: Yes
Status: Disabled
Deactivation reason: Did not fulfill its Prerequisites:
   -BsonSerialization not enable since serialization definition not detected.
Name: JsonSerialization
Version: 5.2.9
Enabled by Default: Yes
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: XmlSerialization
Version: 5.2.9
Enabled by Default: Yes
Status: Disabled
Deactivation reason: Did not fulfill its Prerequisites:
   -XmlSerialization not enable since serialization definition not detected.
Name: MsmqTransportConfigurator
Version: 5.2.9
Enabled by Default: No
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: TimeoutManager
Version: 5.2.9
Enabled by Default: No
Status: Enabled
Dependencies: [TimeoutManagerBasedDeferral]
Startup Tasks: None
Name: Sagas
Version: 5.2.9
Enabled by Default: Yes
Status: Disabled
Deactivation reason: Did not fulfill its Prerequisites:
   -No sagas was found in scanned types
Name: SecondLevelRetries
Version: 5.2.9
Enabled by Default: Yes
Status: Enabled
Dependencies: [ForwarderFaultManager]
Startup Tasks: None
Name: DataBusFileBased
Version: 5.2.9
Enabled by Default: No
Status: Disabled
Deactivation reason: Did not meet one of the dependencies: [DataBus]
Name: StorageDrivenPublishing
Version: 5.2.9
Enabled by Default: No
Status: Enabled
Dependencies: None
Startup Tasks: None
Name: MessageDrivenSubscriptions
Version: 5.2.9
Enabled by Default: No
Status: Enabled
Dependencies: None
Startup Tasks: None

编辑＃2：

在应用David的建议并将配置保持在最低限度之后，仅当使用MsmqPersistence而不是InMemoryPersistence时，我仍然会遇到异常。我还没有尝试过其他持久性存储。

具有完整总线（不是SendOnlyBus）的MVC应用程序抛出此异常，并配置如下：

    public void ConfigureServiceBus( IContainer container, IAppBuilder app )
    {
        var busConfiguration = new BusConfiguration();

        busConfiguration.UseContainer<AutofacBuilder>( c => c.ExistingLifetimeScope( container ) );
        busConfiguration.EnableInstallers();

        var inc = AllAssemblies.Matching( "Company." )
                                            .And( "NServiceBus" )
                                            .And( "ServiceControl" );
        config.AssembliesToScan( inc );

        config.UsePersistence<MsmqPersistence>();
        config.UseSerialization<JsonSerializer>();
        config.UseTransport<MsmqTransport>();

        config.EndpointName( endpointName );

        var startableBus = NServiceBus.Bus.Create( busConfiguration );
        startableBus.Start();
    }
  

抛出异常：'System.NullReferenceException'   NServiceBus.Core.dll其他信息：未设置对象引用   到一个对象的实例。

调用堆栈：

  

ServiceBus.Core.dll！NServiceBus.Timeout.Hosting.Windows.TimeoutPersisterReceiver.Poll（object obj）第90行C＃

MVC中的Autofac配置：

public static IContainer ConfigureAutofac( IAppBuilder app )
{
    ContainerBuilder builder = new ContainerBuilder();

    // Register your MVC controllers.
    builder.RegisterControllers( typeof( MvcApplication ).Assembly );

    builder.RegisterType<...>().AsImplementedInterfaces();
    //...

    // Set the dependency resolver to be Autofac.
    IContainer container = builder.Build();

    var resolver = new Autofac.Integration.Mvc.AutofacDependencyResolver( container );

    DependencyResolver.SetResolver( resolver );

    return container;
}

同样，这发生在具有 MsmqPersistence 的MVC应用程序中，该应用程序订阅Some_Endpoint发布的事件。上面提到的WCF主机最初将命令发送到Some_Endpoint。

1 个答案:

答案 0 :(得分：1)

这里似乎有几件事情，所以我会解决一些可能导致问题的要点。

装配扫描

这段代码控制着对NServiceBus重要类型扫描的程序集：

var includesBuilder = AllAssemblies.Matching( "Company.App." );
config.AssembliesToScan( includesBuilder );

如果您偶然排除重要的程序集，这可能会导致奇怪的事情发生。使用AllAssemblies尝试添加NServiceBus程序集，但确保您排除任何ServiceControl插件。

如果可能的话，更容易省略此部分并允许端点扫描目录中的所有程序集。

更好的是：

config.AssembliesToScan(AllAssemblies.Matching("Company.App.")
    .And("NServiceBus")
    .And("ServiceControl"));

或者甚至更好，不要列入白名单，但如果绝对必须使用黑名单，因为你有一些疯狂的程序集，数千种不相关的类型你不想打扰扫描：

config.AssembliesToScan(AllAssemblies.Except("CrazyAssemblies"));

只发送

在您的WCF代码段中，您正在创建一个只发送总线，但您上面有一些奇怪的配置选择：

config.EnableInstallers(); //ensures msmq is created
config.PurgeOnStartup( true ); //only for self-hosted

config.Transactions().Disable();
config.DisableFeature<StorageDrivenPublishing>();

Bus = NServiceBus.Bus.CreateSendOnly( config ); //create SendOnlyBus here

根据定义，仅发送端点不接收消息，因此不会创建队列。不需要EnableInstallers()，因为不需要设置队列。 PurgeOnStartup(true)没有多大意义，因为没有队列可以清除。

此外，您正在谈论传真和超时队列，但是只发送端点无法处理消息，这也意味着没有传真。这些事物的组合可能会导致奇怪的边缘情况。

启用/禁用功能

我看到一些禁用某些功能的电话：

config.DisableFeature<SecondLevelRetries>();    //turn off for in-mem persistence, otherwise could lose messages

config.DisableFeature<StorageDrivenPublishing>();

SecondLevelRetries是需要超时的事情之一，所以如果你禁用它并且没有传奇，我可以看到哪里可能存在一个独特的设置组合，这些设置会导致InMemory超时持久性未被注册，这将是一个错误。

请注意，在功能输出中：

  • 由于TimeoutManager
    • ，InMemoryTimeoutPersistence被禁用
  • 然而，TiemoutManager已启用。这可能可能是一个错误。

您可以随时尝试强制解决问题：

config.EnableFeature<InMemoryTimeoutPersistence>();

但通常最好允许这些功能为自己解决问题，而不是单独启用/禁用它们。

夫妻相关说明：

  1. 禁用SecondLevelRetries以便不丢失消息是一种倒退。使用内存中持久性，您将丢失消息。它只适合开发。对于生产，您应该使用其他持久性选项之一。但是，我可以看到在开发中跳过SLR以便在调试时没有重复异常跟踪的重要性。
  2. 您为什么禁用StorageDrivenPublishing？ MSMQ没有内置的Pub / Sub（如RabbitMQ或Azure Service Bus），因此如果没有此功能，您将无法发布事件。

    3. 其它

    在将Autofac容器传递给NServiceBus之前，它可能与您的Autofac容器的配置方式有关。很难推测，因为我看不到那段代码。

    我试图使用您提供的代码制作一个repro，但我无法让它失败。如果上述任何一个都无法正常工作并且可以进行简单的repro（例如，在简单的Windows控制台应用程序项目中创建总线）那么它应该相当容易修复，或者至少是确保提供更好的错误消息。

    编辑：MsmqPersistence

    使用MsmqPersistence时，你会得到一个NullReferenceException是有意义的。 MsmqPersistence仅包括订阅存储。它不提供其他持久性类型的实现，包括Timeouts，Sagas，Gateway和Outbox。 （我可能错过了一个？）

    无论如何，MsmqPersistence是一个遗物。不要用它！

    对于开发，您可以使用内存。对于其他环境，您应该使用NHibernate或RavenDB。

相关问题
最新问题