RabbitMQ - queue not created

[mikedevbo (Michał Bogdański)]

Hi @frliran

Trying answer for your questions:

@frliran

Why my published events are not queued/handled?

• Check if you have any message handler for published message. If yes check if the Endpoint who owns the message handler has also configured RabbitMQ transport.

@frliran

Why am I not seeing anything in ServiceInsight?

• Based on the part of the exception info:

C:\\BuildAgent\\work\\a93f853f0c1b9532\\src\\NServiceBus.Core\\Transports\\Msmq\\MsmqMessageDispatcher.cs:line 89

• I guess that somewhere there is still MSMQ configuration so NServiceBus try to send Heartbeats through MSMQ transport and not through RabbitMQ transport.

@frliran

I’ve noticed that it says that a queue named “particular.servicecontrol” does not exist, so I’ve added it to my RabbitMQ instance manually (Just click on “Add queue” and entered the queue name).

• You shouldn’t create “particular.servicecontrol” yourself. If you don’t see this queue in your RabbitMQ environment make sure that you select RabbitMQ transport during configuration ServiceControl instance in ServiceControl Management Utility.

I assume from this topic that the sample code works properly in your Rabbit environment. You can try configure ServiceControl and ServiceInsight to see messages from the sample code. After that you will be sure that potential errors/exceptions/not working issues/… will be associated with the code migration changes.

Hope this help.