![]() 09:40:55,709 DEBUG MassTransit.ServiceContainer - Starting bus service: ![]() 09:40:55,708 DEBUG MassTransit.ServiceContainer - Starting bus service: 09:40:55,658 DEBUG - Adding subscription for GetMessageTraceList on rabbitmq://localhost/AsiPort_UploadListener_control to rabbitmq://localhost/AsiPort_UploadListener_control 09:40:55,458 DEBUG MassTransit.ServiceContainer - Starting bus service: 09:40:55,457 DEBUG - Starting Consumer Pool for rabbitmq://localhost/AsiPort_UploadListener 09:40:54,976 DEBUG MassTransit.ServiceContainer - Starting bus service: 09:40:54,924 DEBUG - Starting Consumer Pool for rabbitmq://localhost/AsiPort_UploadListener_control 09:40:52,242 DEBUG - Creating ControlBus at rabbitmq://localhost/AsiPort_UploadListener_control 09:40:52,240 DEBUG - Configuring control bus for rabbitmq://localhost/AsiPort_UploadListener at rabbitmq://localhost/AsiPort_UploadListener_control 09:40:52,185 DEBUG MassTransit.SagaSubscriptionConfiguratorExtensions - Subscribing Saga: 09:40:51,218 WARN - the custom type '' handled by '' is not Serializable: 09:40:48,424 DEBUG MassTransit.ConsumerSubscriptionExtensions - Subscribing Consumer: (using supplied consumer factory) 09:40:48,423 DEBUG MassTransit.ConsumerSubscriptionExtensions - Subscribing Consumer: (using supplied consumer factory) 09:40:48,422 DEBUG MassTransit.ConsumerSubscriptionExtensions - Subscribing Consumer: (using supplied consumer factory) 09:40:48,421 DEBUG MassTransit.ConsumerSubscriptionExtensions - Subscribing Consumer: (using supplied consumer factory) 09:40:48,367 DEBUG MassTransit.ConsumerSubscriptionExtensions - Subscribing Consumer: (using supplied consumer factory) 09:31:15,184 INFO - Starting Upload Listener Service If this is normal is there a way for me to defer processing of messages until ALL consumers are registered? Is this normal behavior or have I missed something during setup (snip of the setup below). Those messages never reach a consumer and are lost forever (not even on error queue). This makes the system drop messages and that is something we just can't afford.īelow is part of the log during startup, note the three little nasty SKIP messages (at 09:40:56,073) in the middle of the subscription setup. ![]() It looks like the InboundRabbitMqTransport is starting to process messages before all defined consumers are registered. I have one subsystem that generates messages and an other system that consumes those messages into sagas.Īll of this works as a charm as long as both subsystems are up and running, but if I take the consumer offline and let the queue fill up with pending messages and then restart the consumer I get a weird behavior. I'm developing a system that uses RabbitMQ and persistant queues. On Tuesday, J2:21:12 PM UTC+2, Erik Rydgren wrote: Hi!
0 Comments
Leave a Reply. |