Implementing synchronous request response behaviour with JMS

i have a requirement wherein i send a list of tasks to be executed (this has to be executed in parallel so taking the JMS route) and should wait for the results of al these tasks. How could i do this with JMS? I need JMS since the originally these tasks was being done using threading and since in j2ee it is not advisable to spawn threads we are planning to use JMS so that we can have concurrency that is done by the container. can someone please tell how can i simulate this synchronous request-response paradigm using JMS?

It may not be great idea however possibility of State full session bean can be explored.
State full session bean will send all 100 tasks to JMS queue without waiting for the result. There will be another JMS program (Say ResponseCollector) which will listen on queue for all responses. Once ResponseCollector collects all the responses, it will trigger the state full session bean again.
You can use some properties in JMS header to discriminate between the request and response on same queue and apply the message selector.

Similar Messages

Implementing synchronous request/response for an asynchronous service (JMS)

Hi,
 I've to consume soap/jms service from an external application.
 The requirement is to consume it synchronous, meaning, the thread should wait for response.
 
 I.e :
 
 void service(){
 String id = generateCorrelationID();
 Message msg = createRequest(id,...);
 // send the message to the request queue
 sendMesageToRequestQueue(msg);
 Message responseMsg = null;
 // search for the response, if is not found suspend the thread, then search again ...
 do {
 responseMsg = searchMessageInResponseQueue(id);
 if(responseMsg == null) {
 <Thread>.sleep(xxx)
 }
 } while (<messageIsNotFound>)
 }
 
 my application is J2EE 1.3.
 Is it reasonable? am I going to face with deadlocks? locking issues? ...
 
 Thanks,

Assuming synchronous receipt is absolutely necessary, I would rather use JMS synchronous call with timeout on QueueReceiver to receive message rather than spinning in a loop.
 receive(long timeout)

How to implement request/response domain in JMS

hi friends,
I need help regarding implementing request/response domain
in jms.please help me.

See the TopicRequestor and QueueRequestor helper classes in the JMS API.
FWIW there's a POJO based request/response implementation using JMS here...
http://lingo.codehaus.org
you might find the source code useful as it does efficient request/response in a highly concurrent way using JMS under the covers.
James
http://logicblaze.com/

Publish/subscribe in a request/response manner with WCF?

Is it possible to make WCF service work in request/response manner using WCF duplex channels?
Or is there any kind of automatic correlation between the messages when using WCF?
I want to be able to attach WCF service to a topic, and when a request comes, the service to return result, that will be transformed to brokered message and returned over the bus to the caller.
Thanks in advance!

It could help, If there is a way to bind a relay endpoint to a topic...
The scenario in details: I have a service that extracts an object from a database by given identifier. I want to be able to activate that service with a message over a topic. That part is OK, I've did it. But I want the service to return the extracted
value over the topic (or another topic) but I do not want to change the service contract to be OneWay - for interoperability, I need the method in question to take one argument and return object.
So that's why I am searching for a way to bind one message to call the service's method and when it is ready to transform the result in another message and publish it back on the bus.

TemporaryQueue communication - Request/Response messaging in JMS

Not able to make simple JMS application with the following steps run
Start the Server
Start the Client
The Client creates a temporary queue and sends the name to the server
Server receives message and sends a test message back.
Client NEVER receives the test message
Can someone provide me appropriate sample example in this regard. Using "oc4j_extended_101320"
Thanks
sunder
Note the server recives the request and logs the message
but client doesnt consume the message.
Here is client code
package project1;
import java.rmi.*;
import java.util.*;
import javax.jms.Connection;
import javax.jms.JMSException;
import javax.jms.MapMessage;
import javax.jms.Message;
import javax.jms.MessageConsumer;
import javax.jms.MessageListener;
import javax.jms.MessageProducer;
import javax.jms.Queue;
import javax.jms.QueueConnection;
import javax.jms.QueueConnectionFactory;
import javax.jms.QueueSender;
import javax.jms.QueueSession;
import javax.jms.Session;
import javax.jms.TemporaryQueue;
import javax.jms.TextMessage;
import javax.naming.*;
public class TestClient {
private QueueSender sender;
private Session session;
private Connection connection;
private MessageConsumer consumer;
private MessageProducer producer;
* Constructor: Setup JMS for publishing
public TestClient() {
try {
Context ctx = getInitialContext();
System.out.print("env " + ctx.getEnvironment());
QueueConnectionFactory conFactory =
(QueueConnectionFactory) ctx.lookup("jms/QueueConnectionFactory");
Queue chatQueue = (Queue) ctx.lookup("jms/TestQueue");
// Create a JMS connection
connection = conFactory.createConnection();
// Create a JMS session object
session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
TemporaryQueue replyQueue = session.createTemporaryQueue();
TextMessage textMsg = session.createTextMessage();
textMsg.setText( "How r u dude!!!!!!!");
textMsg.setJMSReplyTo(replyQueue);
textMsg.setJMSExpiration(40000l);
System.out.println("\nsender 1 ========== >>>>> " + replyQueue.getQueueName());
consumer = session.createConsumer(replyQueue);
System.out.println("sender 2========== >>>>> " + replyQueue.getQueueName());
System.out.println("sender 2a========== >>>>> \n" + textMsg.getJMSMessageID() +"\n");
System.out.println("sender 2b========== >>>>> \n" + textMsg.getJMSCorrelationID() +"\n");
producer = (MessageProducer) session.createProducer(chatQueue);
producer.send(textMsg);
System.out.println("sender 3a========== >>>>> \n" + textMsg.getJMSMessageID() +"\n");
System.out.println("sender 3b========== >>>>> \n" + textMsg.getJMSCorrelationID() +"\n");
} catch(Exception e) {
e.printStackTrace();
finally {
* Method: sendmail(Map mail)
public void sendmail() throws Exception {
Message respmessage = (TextMessage )consumer.receive();
System.out.println("sender 3========== >>>>> " + ((TextMessage)respmessage).getText());
private Context getInitialContext() throws NamingException {
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.evermind.server.rmi.RMIInitialContextFactory");
env.put("java.naming.provider.url", "ormi://localhost");
env.put("java.naming.security.principal", "oc4jadmin");
env.put("java.naming.security.credentials", "welcome1");
return new InitialContext(env);
* Static Method: java com.customware.client.EmailClient to_addr [from_addr] [subject] [body]
public static void main(String args[]) throws Exception {
System.out.println("\nBeginning EmailClient\n");
TestClient client = new TestClient();
client.sendmail();
MDB code
package project2;
import javax.ejb.CreateException;
import javax.ejb.EJBException;
import javax.ejb.MessageDrivenBean;
import javax.ejb.MessageDrivenContext;
import javax.jms.Destination;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.MessageProducer;
import javax.jms.Session;
import javax.jms.ConnectionFactory;
import javax.jms.Connection;
import javax.jms.MapMessage;
import javax.jms.TextMessage;
public class MessageDrivenEJBBean implements MessageDrivenBean,
MessageListener {
private MessageDrivenContext _context;
private javax.jms.ConnectionFactory connectionFactory;
private javax.sql.DataSource dataSource;
public void ejbCreate() throws CreateException {
dataSource = ResourceFactory.getInstance().getPricingDS();
//java:comp/env/jdbc/PricingDS
connectionFactory = ResourceFactory.getInstance().getPricingRespQueueCF();
public void setMessageDrivenContext(MessageDrivenContext context) throws EJBException {
_context = context;
public void ejbRemove() throws EJBException {
public void onMessage(Message message) {
TextMessage msg = null;
Connection connection = null;
try {
if (message instanceof TextMessage) {
msg = (TextMessage) message;
System.out.println
("Dood Message "
+ msg.getText());
connection = connectionFactory.createConnection();
Destination replyDest = message.getJMSReplyTo();
System.out.println
("Dood Reply Queue "
+ msg.getJMSReplyTo());
String replyMsgId = msg.getJMSMessageID();
Session session = connection.createSession(true, 0);
System.out.println("Creating producer!!!!!!!!"+ replyDest);
System.out.println("Creating consumer!!!!!!!! ID\n\n"+ replyMsgId);
System.out.println("Creating consumer!!!!!!!!COR ID\n\n"+ msg.getJMSCorrelationID());
MessageProducer producer = session.createProducer(replyDest);
TextMessage replyMsg = session.createTextMessage();
replyMsg.setText("Response Message!!!!!!!! Good Job" );
replyMsg.setJMSCorrelationID(replyMsgId);
producer.send(replyMsg);
System.out.println("Creating producer!!!!!!!!ID\n\n"+ replyMsg.getJMSMessageID());
System.out.println("Creating producer!!!!!!!!COR ID\n\n"+ replyMsg.getJMSCorrelationID());
producer.close();
session.close();
} else {
System.out.println
("Message of wrong type: "
+ message.getClass().getName());
} catch (Throwable te) {
te.printStackTrace();
finally {
try{
if(connection!=null)
connection.close();
} catch(Exception e) {
Message was edited by:
user565613

You created a transacted session on the server, and then never committed the transaction. Since the transaction was not committed before the session was closed, it is automatically rolled back as per the JMS spec. Either call commit on the session or use a non-transacted session (e.g., use session-creation paramters of "false, Session.AUTO_ACKNOWLEDGE").
-Jeff

Best way to implement request-response and still reliability

          HI,
          what is the best way to implement a request -response paradigm and still have
          the reliability that message will be 100% processed and give response...do i need
          to create the permanant queues with storage..
          anybody gives suggestions..
          Akhil


Hi Akhil,
          Temporary destinations can only store non-persistent messages
          as per JMS spec - so they are not useful for reliable for holding
          responses that must survive longer than the life of the
          interested client. For persistence, you will need to use configured
          queues or durable subscriptions. For detailed
          discussion of request/response, I suggest reading the "WebLogic JMS
          Performance Guide" white-paper on dev2dev.bea.com. If you
          have many clients, or expect large message back-logs,
          there can be a performance impact when using selectors...
          FYI: There is a new pub/sub subscriber index enhancement
          that is available in 8.1 and
          in the latest service-packs for 6.1, 7.0.
          "Indexing Topic Subscriber Message Selectors To Optimize Performance"
          http://edocs.bea.com/wls/docs81/jms/implement.html#1294809
          This may be useful.
          Tom, BEA
          Akhil Nagpal wrote:
          > HI,
          > what is the best way to implement a request -response paradigm and still have
          > the reliability that message will be 100% processed and give response...do i need
          > to create the permanant queues with storage..
          >
          > anybody gives suggestions..
          > Akhil

Creating synchronous publisher with JMS

I wonder, if it's possible to "synchronously publish" the messages with JMS pub/sub model. "Synchronously publish" - that is to say, when a message has been published (publish() method invoked with the message), the thread waits until the message is successfully consumed by all the registered subscribers (i.e. is acknowledged).
In other words, I would like to be sure that the message has been consumed successfully before I send the next message.
Thanks.

Thank you once more for your time and explanations.
Probably, I might want to use not a JMS-based system, but rather an event system, similar to Spring events framework, because I'm interested rather in a solid-made thread-safe message dispatcher library (not necessarily across network - inside one process would be enough), than in a separate message broker service.
As for "hardly acceptable" - indeed, I don't want any of my classes to be tightly bound to any broker-specific logic, one of which is the necessity to notify the message sender about the fact that the message had been consumed.
For example, when using any simple event-system, similar to what AWT presents, a MessageListener implementation is only limited by the obligation to implement one-method interface (kind of actionPerformed, mouseClicked - generally saying - eventOccured) and nothing else. And the side, which raises the event (publisher/sender) and sends the message, naturally waits for the eventOccured method to return (unless the method is launched in a separate thread). This would be the ideal situation for me.
The reason why I decided to spend time playing with JMS was that I needed a solution which could stand multi-threading, scaling and high-load situations. And at this point it is normally preferred to select an existing time-proven solution rather then inventing anything by my own :).
Thanks again and all the best to you as well!

No synchronous Request/Reply option in B2B config wizard step 5 of 7 ?

I have a customer running SOA Suite 11.1.1.5 who has created a BPEL process
and added a B2B partner link to the reference swim lane.
They want to send a 270 document to a partner and receive a 271 on the same HTTP Channel as a Sync Req/Reply
When the customer runs the B2B wizard, it successfully connects to their WLS Server and at
Step 5 of 7 in the wizard they see radio buttons for
o Send
o Receive
They do not have radio buttons further down for
o Synchronous Request/Response
o Outbound
o Inbound
Does anyone have any ideas why not?
I have a sample running on my local server which is also 11.1.1.5 and
the Synchronous Request/Response radio buttons do appear.
thanks
Bob

Bob,
I don't think PS4 (11.1.1.5) has this option available -
http://docs.oracle.com/cd/E21764_01/integration.1111/e10229/intro_ui.htm#CHDEGEEB
Please re-check your local setup version.
Regards,
Anuj

HTTP Channel request-response

Hi,
I have configured HTTP channel for synchronous request response (syncresponse=true in additional headers). I have to send an outbound Invoice to TP via http, get the response back and process it as an email. I have the outbound and inbound agreements set and it works fine. The issue is that I am unable to create a correlation between the request and response (invoice request corresponds to which response). Is there any setting to achieve this?
Thanks in advance.

This looks to be known issue. Similar bug was reported for
Bug 17304428 - hcfpmlr: sync 271 response does not set reference to outbound 270
There could be one possible solution of using correlation xpaths defined into the document definition, however, this being a sync transfer, it might happen that the outbound msg's xpaths are not persisted into the DB and the response msg xpath for correlation wouldn't find this.
Hence, for the correlation of sync request and response to work by default the bug should get fixed. Please indicate the same in the bug if fix is required.

Does any one implemented solution for httpservlet request/response object in IWSDLInterceptor implemented class?

I am trying to handle Producer not available situation in which I am using Interceptor IWSDLInterceptor in WLP 10.3.4. I am able to retrieve exception using onWSDLException but from here if I have to forward my pageURL object I need httpservlet request and response. I tried my own filter class to have its own customize request and also tried it out all other Interceptor to see if any one can handle IOException. I did manage to throw my own Customize exception but that also did not work out as Page does not have any backing file or any supportive Controller class.
Does any one implemented solution for httpservlet request/response object in IWSDLInterceptor implemented class? or do we have any specific documentation in regards to this? As I am not able to find much martial on IWSDLInterceptor except Java API from Oracle and article defining Two way SSL handshake Producer.
Any kind of help is appreciated.
Thanks
PT

Thanks Emmanuel for your response but render behavior is not available for IWSDLRequestContext/IWDSLResponseContext object which IWSDLInterceptor uses for implementation.
Let me put my question in little simpler manner. May be my approach to the problem is not proper.
Problem : Handle Producer Not available (no application exists on server) on consumer side.
So far tried approach : Producer is not running then I am able to handle that TransportException at IInitCookieInterceptor/IHandleEventInterceptor onFault behaviour but in the case of Producer not even exists Consumer try to get WSDL fetch operation and failed with FileNotFoundException.
To handle this exception, I used IWSDLInterceptor which is available under IWSDLInterceptor.OnWSDLException (Oracle Fusion Middleware Java API for Oracle WebLogic Portal)
I am able to catch the exception but problem arise when application needs to forward at specific page/render portlet for this situation. For that it required request/response object but IWSDLInterceptor does not give any kind of instances to redirect request as there is no direct access to HTTPServlet request/response object.
I tried my custom request object to use there. I tried out custom filter object of IWSDLrequestContext. nothing works.
One approach works is to put producer WSDL file at consumer level. But in that, you need to handle different producer files for different environment. Which I don't think its a good approach.
eAny one Let me know if my approach to the problem/scenario is wrong. Or if I am missing out any other supporting interface which also required to handle this scenario. or I am using wrong interface for this scenario.
Thanks for your help in advance.
PT.

JMS Transport, Transactional, asynchronous request-response

Hi again :)
I have weblogic web service with jms transport and have chosen session bean implementation.
I'm testing transactional processing now.
Required feature is to put getting request from queue and processing it in web service in one transaction.
During tests I have noticed that:
When I throw RuntimeException from my web service method the message doesn't come back to the queue.
When I try to sessionContext.setRollbackOnly(); I get an error
javax.ejb.EJBException: EJB Exception: : java.lang.IllegalStateException: [EJB:010158]Illegal attempt to call EJBContext.setRollbackOnly() from an EJB that was not participating in a transaction.
When I deploy web service I get the following warning:
<Warning> <EJB> <> <AdminServer> <[STANDBY] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1238752023176> <BEA-010212> <The EJB 'EventNotifierServiceEJB(Application: portal, EJBComponent: EventNotifierService-1.0-SNAPSHOT.jar)' contains at least one method without an explicit transaction attribute setting. The default transaction attribute of Supports will be used for the following methods: local[publish(package.PackageType)] >
And putting @TransactionAttribute(TransactionAttributeType.MANDATORY) doesn't change this.
So It seems that transactions doesn't work by default.
I turned on XA in my own jms connection factory used by web service but this didn't help.
Looking in weblogic documentation I have found the following sentences:
In (http://e-docs.bea.com/wls/docs103/webserv_adv_rpc/jmstransport.html)
"If you have specified that the Web Service you invoke using JMS transport also runs within the context of a transaction (in other words, the JWS file includes the @weblogic.jws.Transactional annotation), you must use asynchronous request-response when invoking the service. If you do not, a deadlock will occur and the invocation will fail."
In (http://e-docs.bea.com/wls/docs103/webserv_adv_rpc/asynch.html)
"The asynchronous request-response feature works only with HTTP; you cannot use it with the HTTPS or JMS transport."
For me these two sentences are in conflict.
Currently I'm trying to use just transactional annotation without asynchronous request-response but the risk of deadlocks doesn't sound good for me.
BTW I have Oneway annotation in my web service method, I'm not sure if this changes something.
I'll be grateful for any help in resolving this problem.
Edited by: user10930859 on Apr 3, 2009 3:49 AM

Hi Karthik-
You can link the corelation-id..
Make you third-party application to receive Message-id from JMSRequestQueue and send this message id as correlation-id to JMSResponseQueue. I guess it would work we have tried this as POC.
Regards,
Ramesh

JMS Request/Response example

Hi
I am trying to implement a JMS Request/Response example on glassfish, but i am not getting the correct behaviour.
My code is below. I am sending a message to a queue and adding the setJMSReplyTo another queue. I call the recv.receive(10000); and wait for the messages to be received. But this call blocks the current thread and the MDB that i orginally sent the message to only gets executed after the recv.receive(10000); has timed out after 10 seconds.
Can someone confirm that my code is correct or am i doing something wrong?
Connection connection = null;
Session session = null;
String text = "hello";
try {
System.out.println("Sending " + text);
connection = searchDestFactory.createConnection();
session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
MessageProducer messageProducer = session.createProducer(searchDest);
TextMessage tm = session.createTextMessage();
tm.setText(text);
tm.setJMSReplyTo(destQueue);
messageProducer.send(tm);
System.out.println("Sent " + text);
MessageConsumer recv = session.createConsumer(destQueue);
connection.start();
Message m = recv.receive(10000);
tm = (TextMessage) m;
if(tm != null) System.out.println(tm.getText());
else System.out.println("No message replied");
} catch (JMSException ex) {
System.out.println(ex);
Thanks Glen
Edited by: glen_ on Jun 16, 2008 6:13 AM
Edited by: glen_ on Jun 16, 2008 6:13 AM
Edited by: glen_ on Jun 16, 2008 6:14 AM

Glen,
I have never attempted to use the messaging service the way you have, namely a single instance as both sender and receiver, but I noticed that you do send the message before you register your Consumer. My first and easiest suggestion would be to simply move your consumer block (I would move both lines) above the producer block and try again.
If that attempt fails, I would implement a MessageListener, once again before the producer block and allow it to handle received messages (no need for recv.receive(10000);)
Example:
    public class QueueMessageListener implements MessageListener {
        public void onMessage(Message message) {
            try {
                System.out.println(String.format("From Glassfish: %s received a %s of type %s.", m_Queue.getQueueName(), message.getClass().getName(), message.getJMSType()));
                System.out.println(printJMSMessage(message));
            } catch (JMSException ex) {
            //handle message here
    }and somewhere before the producer block:
            m_msgListener = new QueueMessageListener();
            m_msgConsumer = m_Session.createConsumer(m_Queue);
            m_msgConsumer.setMessageListener(m_msgListener);
            m_Connection.start();I feel like I've done my good dead for the day :)
-Jerome BG

Request and Response Scenario for JMS adapter

Hi,
I am working on IDOC-XI-JMS, JMS(sender)- XI - JMS (receiver)scenario and this is going to be real time. If any record is update in customer master then that record will be sent to JMS provider MQ series and lock the record in the legacy system and then legacy system unlock and send back a message that this has been unlocked.
This would be request response message, anyone tell me how this can be achived. I think I may have to use BPM for this kind of processing. Can anyone tell me the steps to achive the BPM for such processing.
Regards
Please reply back
Edited by: hema Mehta on May 23, 2008 2:05 AM

Hi Hema,
Reward points if this helps
Step by Step Porcess of JMS Synchronous Scenario without BPM: Correlation Settings and Transactional JMS Session
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b028f6f6-7da5-2a10-19bd-cf322cf5ae7b
How To Correlate JMS Messages
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8060448a-e56e-2910-f588-9af459e7ce21
Async/Sync Communication using JMS adapter without BPM
/people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
STEPS in BPM for synchornous.
Reward points if this helps
Regards
Pragathi.

Blocking Request/Response JMS model

Hi everyone !
I'm starting to write a JMS application and I'm having some doubt about the request/response model enabled by the replyTo() method and CorrelationID field. As far is I know JMS is intended to let the client be free from the server's response by posting it's message on the queue and start doing some other work. But supposing the client needs a response from the server(a MDB) after the processing of the message I wonder how would him receive this response, assuming there is a second queue for posting the response messages. Simply using the MessageConsumer.receive() the client will be blocked, killing all the purpose of the model(even with timeout). So I wonder, should I create a second MDB just to handle the response queue ? This would left me with an RPC message producer, a MDB Message consumer (of the request message), and a MDB Message consumer (on the response queue). Is this a normal approach or is there something better ?
Thank you !

Simply using the MessageConsumer.receive() the client will be blocked, killing all the purpose of the model(even with timeout).
You have to send the message and wait for the response in two separate transactions. For example:
// Start create and send transaction
ctx.getUserTransaction().begin();
connection = connectionFactory.createQueueConnection();
connection.start();
session = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
final Message request = // create message
final Queue tempQueue = session.createTemporaryQueue();
request.setJMSReplyTo(tempQueue);
final QueueSender sender = session.createSender(destination);
sender.send(request);
ctx.getUserTransaction().commit();
// End create and send transaction
// Start receive transaction
ctx.getUserTransaction().begin();
final QueueReceiver receiver = session.createReceiver(tempQueue);
final Message response = receiver.receive(TIMEOUT);
ctx.getUserTransaction().commit();
// End receive transaction
// process response

Asynchronous Request-Response in JMS using OSB 11g

Hi All,
I am using OSB11g.
I have a scenario where I want to post a request into a JMS requestQueue, and without waiting for the response, should continue posting messages into the queue.
The response will be posted by a third party into a JMS responseQueue.
How to go ahead with this scenario? Is there any way to link the request & response in asynchronous calls like this?
Thanks in advance!!
Regards,
Karthik

Hi Karthik-
You can link the corelation-id..
Make you third-party application to receive Message-id from JMSRequestQueue and send this message id as correlation-id to JMSResponseQueue. I guess it would work we have tried this as POC.
Regards,
Ramesh

Implementing synchronous request response behaviour with JMS

Similar Messages

Maybe you are looking for