У меня есть хост WCF (IIS), где я получаю это исключение во время настройки NServiceBus:
Возникло исключение: «Autofac.Core.Registration.ComponentNotRegisteredException» в NServiceBus.Core.dll
Дополнительная информация: запрошенная служба «NServiceBus.Timeout.Core.IPersistTimeouts» не зарегистрирована. Чтобы избежать этого исключения, либо зарегистрируйте компонент для предоставления службы, проверьте регистрацию службы с помощью IsRegistered(), либо используйте метод ResolveOptional() для разрешения дополнительной зависимости.
Я использую NSB 5.2.9 с постоянством в памяти и транспортом MSMQ.
Это моя конфигурация для собственного хоста WCF (IIS). Нет App.config! **Это вызывается после регистрации Autofac в global.asax:
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
, но любой метод, который я нашел, помечен как устаревший и не работает.
EDIT #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:
После применения предложений Дэвида и сведения конфигурации к минимуму я по-прежнему получаю исключение ТОЛЬКО при использовании MsmqPersistence вместо InMemoryPersistence. Я не пробовал другие постоянные хранилища.
Это исключение вызывается приложением MVC с полной шиной (не SendOnlyBus) и настроено следующим образом:
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#
Конфигурация Autofac в MVC:
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;
}
Опять же, это происходит в приложении MVC с MsmqPersistence, которое подписывается на события, публикуемые Some_Endpoint. Упомянутый выше хост WCF изначально отправляет команды этой Some_Endpoint.