1
votes

I'm working on mule 3.5, rabbitmq connector 3.6 and RabbitMQ 3.6.0 When I deploy my application, mule does not create some consumers on my queues, but if I redeploy my app in multiple times it would create all of listeners completely.
Here is part of my code:
Amqp connector:

<amqp:connector name="amqpRabbitMQConnector" host="${rabbitmq.host}" username="${rabbitmq.username}" password="${rabbitmq.password}" validateConnections="true" requestedHeartbeat="60"  activeDeclarationsOnly="true">          
<reconnect-forever frequency="2000" blocking="false"/>  
</amqp:connector>

Inbound endpoint:

<amqp:inbound-endpoint queueName="${queue.businessSearchRequest}" exchange-pattern="one-way"connector-ref="amqpRabbitMQConnector"/>  

Outbound endpoint:

<amqp:outbound-endpoint connector-ref="amqpRabbitMQConnector" exchangeName="${exchange.bizSearchResponse}"                             exchangeType="topic" exchangeDurable="true" routingKey="${core.routing.key}"/>  

Actually, my exchanges bound to my queues in rabbitmq and I can see that the exchange put message to the queue and the queue depth increases but in rabbitmq browser there is no consumer which listens to the queue hence, mule can not process it.

1
Hi, I think you need to provide more details like Mule version connector version, your flow configuration files and so on. Otherwise will be hard to help you.Mauro Rocco
Of course, you're right. My mule version is 3.5.0, amqpconnector is 3.6.2 and this is my connector:Sima
@MauroRocco Hi, you're right. This is my connector code: <amqp:connector name="amqpRabbitConnector" host="${host}" username="${username}" password="${pass}" validateConnections="true" requestedHeartbeat="60" activeDeclarationsOnly="true"> <reconnect-forever frequency="2000" blocking="false"/> </amqp:connector>Sima
Hi @Sima, first of all I suggest you edit your question so people will better read it. Second you are showing me the connector conf only but what about inbound and outbound message processor where you normally put queue names and so son. The best will be to copy and past the full xml of your flow.Mauro Rocco
@MauroRocco Actually I'm new to stackoverflow, but I did my best :), hope it be informing enoughSima

1 Answers

0
votes

The problem was that some of queues listeners registered before AmqpMessageReceiver initializes. I changed my xml orders and the problem solved.