Building a rest service that pushes into a jms queue - howto?

[3r4sm0]

Hi!

I built a service that can be invoked by a rest binding and is implemented by a bean implementation.

I would like to push into a jms queue upon a rest request, so that i can activate an asynchronous elaboration simply by invoking a restful web service.

All works great but the jms invocation looks like to be synchronous, that is my bean is blocked until the jms consumer has not finished its job.

my bean is

======================

@Service(MyServiceBean .class)

public class MyServiceBean implements MyService{

  @Inject @Reference("MyServiceJMS")

  MyServiceJMS service;

  @Override

  public int operation(Integer a) {

  service.operation();

  return 0;

  }

}

======================

when I invoke it through the web browser, the page loads until the service.operation() line has not finished.

I was expecting that service.operation() would have pushed into the jms queue and returned quickly. Any help?

Thank you

[igarashitm]

How does your consumer application look like? You showed above is a sender side, and sending a message to the JMS queue itself is a synchronous action. When we say asynchronous on JMS, it just means the receiver receives a message asynchronously from a queue.

[3r4sm0]

I simply made another service with a JMS binding.

maybe I could call

service.operation()

in a separate thread, but I don't think it's the best pratice

[igarashitm]

You mean service.operation() on sender doesn't return until the consumer application receives the message? That shouldn't happen. If you add Thread.sleep(5*60*1000) in the consumer application, service.operation() in sender application actually waits 5 minutes? If so, JMS itself doesn't cause it, but there should be something synchronizing between sender and consumer.

[3r4sm0]

yes, that's it!

the sender awaits.

If I use plain jms api, instead of the injected service, everything goes fine.

[igarashitm]

Can you attach your application and a testcase which demonstrate that behavior?

[3r4sm0]

here it comes!

http://www.megafileupload.com/en/file/493957/RestToJMS-rar.html

[mageshbk]

Sorry to barge-in Tomo! I did not yet look at the sample application, but my guess is that the REST interface is designed as a request-response MEP, in essence it has a return value. So if user does not want to wait for a response from the Bean service, he can mention either the REST binding to be one-way by having no return value or the Bean interface to be one-way having no return value. Just my 2 cents!

regards,

Magesh

[3r4sm0]

it worked!

i just set my jms consumer method to void

thank you!