Spring AMQP + RabbitMQ RPC How to execute/delegate different methods in a class - rabbitmq

Question

I spent the entire day trying to get this to work. I've been following the tutorial 5 & 6 for Spring AMQP in the RabbitMQ tutorials page.
Is it possible for a single class to execute a different method based on some property? E.g. Routing key?
I've tried this so far to no avail:
#RabbitListener(bindings = #QueueBinding(
value = #Queue(value = "requests"),
exchange = #Exchange(value = "ourexchange"),
key = "doFunc1")
)
public String func1(long id) {
System.out.println("func1 " + id);
return "func1 " + id;
}
#RabbitListener(bindings = #QueueBinding(
value = #Queue(value = "requests"),
exchange = #Exchange(value = "ourexchange"),
key = "doFunc2")
)
public String func2(long id) {
System.out.println("func2 " + id);
return "func2 " + id;
}
In my client I did this:
public void send() {
System.out.println(" [x] Get func1( account_id: " + accountId + ")");
String response = (String) template.convertSendAndReceive
("ourexchange", "doFunc1", accountId);
System.out.println(" [.] Got '" + response + "'");
System.out.println(" [x] Get func2( account_id: " + accountId + ")");
String response = (String) template.convertSendAndReceive
(exchange.getName(), "doFunc2", accountId);
System.out.println(" [.] Got '" + response + "'");
}
I've got it "somewhat" to work but it appears to work in a round-robin fashion where the first method is called then the next one.
I've already considered the explanation here: Single Queue, multiple #RabbitListener but different services
But since the signatures of both methods look identical I'm not sure it's possible.
Do note that I'm a beginner to the concepts of AMQP (like I've just read about the basics today). Am I doing this right or am I misunderstanding the usage?

Answer 1

The #RabbitListener infrastructure doesn't perform routing based on the routing key. You should use a different queue for each method and let RabbitMQ do the routing at the exchange level.
Alternatively, if you must use a single queue for some reason, you can pass the RECEIVED_ROUTING_KEY as a #Header parameter to your listener and delegate to different methods from the listener.
I've got it "somewhat" to work but it appears to work in a round-robin fashion where the first method is called then the next one.
That's because RabbitMQ sees 2 consumers and will round-robin the messages. You need to use 2 queues or a single method and do the routing therein.