Using Spring Integration with RabbitMQ

Question

I\'m in the process of developing a messaging interface for one of our applications. The application is a service which is designed to accept a \"Job\", do some processing, and

Answer 1

I'm as much a noob to spring-integration and spring-integration-amqp as you, I suspect, but I did get something working based in part on the one sample project.

For rabbitmq infrastructure, I have the following:

To send a message to rabbitmq, I have the following:

And to receive messages I have the following:

// from rabbitmq to local channel

Some caveats - the documentation of amqp integration in spring-integration says it is possible to to a synchronous send and receive of a return value, but I haven't figured that out yet. When my service-activator method returned a value, it caused an exception to get thrown, putting the message back on rabbitmq (and generating an infinite loop, since it would then receive the message again and throw the exception again).

My BackgroundService interfacde looks like this:

package com.company

import org.springframework.integration.annotation.Gateway

public interface BackgroundService {

    //@Gateway(requestChannel="someOtherMessageChannel")
    public String sayHello(String toWho)

}

You can specify a channel on every method via the annotation if you don't wish to use the default channel configured in the spring bean.

The service attached to the service-activator looks like this:

package com.company;

class TestService {

    public void serviceMethod(String param) {
    log.info("serviceMethod received: " + param");
    //return "hello, " + param;
    }
}

When I had everything wired up locally without rabbitmq involved, the return value was correctly received by the caller. When I went to rabbitmq channels, I got the aforementioned infinite loop when an exception was thrown after returning a value. It is surely possible or else it wouldn't be possible to wire in different channels without modifying code, but I'm not sure what the trick is yet. Please respond with a solution if you figure it out. Obviously, you can put whatever routing, transforming, and filtering you like between the endpoints, as needed.

Don't be surprised if my XML excerpts above have typos in them. I had to convert back to xml from groovy DSL, so I could have made mistakes. But the intent should be clear enough.