Propagate JMS Request Queue to JMS response in Topic

Hi guys
I trying to create a composite application that give me the response for one request queue and receive the response in a topic JMS, but I cant propagate the received response to the composite application. I have the response in the mediator but the BPEL process are waiting for the response.
I working in SOA Suite 11.1.1.2 and WLS 10.2
My composite have a main BPEL process and 2 mediators with Adapters to JMS Queue and JMS Topic
Someone know what I´m doing wrong???
Thanks.

Hi,
The problem as described seems like it is specific to BPEL -- you might want to try posting to the BPEL forum at BPEL
Tom

Similar Messages

I can´t propagate JMS response to Process BPEL

Hi guys
I trying to create a composite application that give me the response for one request queue and receive the response in a topic JMS, but I cant propagate the received response to the composite application. I have the response in the mediator but the BPEL process are waiting for the response.
I working in SOA Suite 11.1.1.2 and WLS 10.2
My composite have a main BPEL process and 2 mediators with Adapters to JMS Queue and JMS Topic
Someone know what I´m doing wrong???
Thanks.

Hi,
Is it one of the possible cases listed in this article: http://forums.adobe.com/docs/DOC-4071?
Thanks,
Wenlan

New to JMS: How to have to Request Queue

hi
I have a problem.
I have integrated Weblogic 10 with Webspere 7.
I am able to communicate between the same using a binding file.
Now, I have one Request Queue in weblogic which in turn connects to the MDB.
how can i have two request Queue.
In my case : I have two swift System which send request to my MDB. when it is only one Incoming Queue,then it is fine.
Can messaging Topic help? any dummies document on these.
please help
Thanks in advances
Suhel

I am not sure I fully understand your application configuration and what you are trying to achieve.
A topic is for an application logic where multiple consumers need to receive a copy of each message that is sent to a destination What. you want to achieve is multiple senders though.
If you don't want the two swift systems to share the same Request Queue, you can configure another queue in WebLogic and deploy another MDB to listen to it. In other words, if you configure 2 request queues, you can deploy 2 MDBs, each listen on one queue. You can also use WebLogic cluster and distributed queues, where multiple physical queues share the same logic jnid name. Then you only need to deploy one MDB.
If you give more details about your goal, you have a better chance to get helpful answers.
Thanks,
Dongbo

con:async-request-queue

Hi,
          I've created the jms-queue, which was described in the manifest.xml, between the <con:async-request-queue> and <con:async-request-error-queue> -tags.
          I've a problem with the async-request-queue... When I send a message, the message is treated right, but it stays on this queue. Normally when a message is send, it gets the message from the specific queue... I really don't get what's wrong...
          Has anyone an idea?
          Thx in advance
          Ann

hi,
thanks for the reply.
Just tell me if my understanding is right. Let us consider the application server is getting the requests. When we Enable Request Flow Control (by selecting the checkbox), we are making the server to put the requests to a queue(if all the threads of the process is busy, it puts it to the queue.). By, low water mark and high water mark, we mention the minimum and maximum amount of requests to be put into a queue.
If i am right, i am getting the following doubt. You have mentioned that this wont work in KXS (that is... appserver will accept any amount of requests). What if the requests exceed the Request Queue High Water Mark? Will the server be continuing to get the requests? Or will it hang?
regards,
desigan

How can we assign more than one request group to a responsibility?

Hi
Can anyone tell me how we can assign more than one request group to a responsibility?
Thanks
SS

Hi SS,
Its not possible, rather you should create a combination of Requests/RequestSets and create a new Request Group.
Regards,
Kiran

How to send a request and get a response through xml

How to send a request and get a response through xml files?

This is the code that works for me. Hope you find it useful.
     public static String sendHttpGetRequest(String endpoint, String requestParameters){
          String result = null;
          // Send a GET request to the servlet
          try{
               // Send data
               String urlStr = endpoint;
               if (requestParameters != null && requestParameters.length () > 0){
                    urlStr += "?" + requestParameters;
               URL url = new URL(urlStr);
               HttpURLConnection conn = (HttpURLConnection) url.openConnection();
               conn.setRequestProperty("Accept", "application/xml");
               // Get the response
               BufferedReader rd = new BufferedReader(new InputStreamReader(conn.getInputStream()));
               StringBuffer sb = new StringBuffer();
               String line;
               while ((line = rd.readLine()) != null){
                    sb.append(line);
               rd.close();
               result = sb.toString();
          } catch (Exception e){
               e.printStackTrace();
          return result;
     }

Request Message field to Response Message

Hi Everyone,
I have a synchcronous scenario, where I have a special requirement that I want to append a Request Message Field in Response Message Structure while sending response to Sender.
Could someone suggest me probable solution, I have come up with using Value mapping table, but I am restricted to use a proxy for dynamic updates to the table??
Regards,
Nipun

Hello,
I have a synchcronous scenario, where I have a special requirement that I want to append a Request Message Field in Response Message Structure while sending response to Sender.
Perhaps the easiest would to to try to ask the endpoint to modify the response such that it contains the request. Otherwise, you can use a logic such as saving into a table and then retrieve the values for the response message mapping.
Hope this helps,
Mark

Is billable a request with a 304 response?

In an azure blob storage account, I would like to know if when a request receives a 304 response, this is counted as a billabable request or not

Hi,
Please have a check on the below link which talks about Understanding Windows Azure Storage Billing – Bandwidth, Transactions, and Capacity.
http://blogs.msdn.com/b/windowsazurestorage/archive/2010/07/09/understanding-windows-azure-storage-billing-bandwidth-transactions-and-capacity.aspx
Hope it helps.
Regards,
Mekh.

How could increase the number of waiting request queue?

how could increase the number of waiting request queue?
thanks,

I assume you're asking because you're getting connection refused exceptions? Set the AcceptBacklog parameter in the config.xml/via the console. Here's a description of the parameter:
http://e-docs.bea.com/wls/docs81/config_xml/Server.html#AcceptBacklog

Dispather request queue and FIFO

Are the request in the request queue processed on the basis of first in first out (FIFO)? thanks.

Yes, The requests are processed on a first-in, first-out basis (FIFO).
Manu

JMS Distributed Destination Topic - how to avoid MDB to recieve duplicates

HELP!!
          I have spent a lot of time looking for an option to move jms on a cluster, finally I can do this using distributed destination, I have two memmbers(Topic) in the distributed destination topic, but when both of them are active, the Message Driven Bean which is deployed on cluster recieves 2 messages instead of 1, anyone please help me to change this to have only one message instead of 2 !!!!!

Make it a Queue or don't deploy the MDB to the cluster. You are seeing
          expected behavior. I have the same situation with a Topic and I deploy my
          MDB to one node in the cluster and have it configured to consume the local
          physical Topic.
          Bill
          "Manav Sehgal" <[email protected]> wrote in message
          news:18024883.1107530318601.JavaMail.root@jserv5...
          > HELP!!
          > I have spent a lot of time looking for an option to move jms on a
          > cluster, finally I can do this using distributed destination, I have two
          > memmbers(Topic) in the distributed destination topic, but when both of
          > them are active, the Message Driven Bean which is deployed on cluster
          > recieves 2 messages instead of 1, anyone please help me to change this to
          > have only one message instead of 2 !!!!!

JMS Durable Distributed Topics

          Please forgive my ignorance if I am doing something silly. I am new to Weblogic
          and JMS, but learning a lot quickly. Any help will be greatly appreciated.
          I am running weblogic 8.1 with no service packs in a development environment only.
          We are trying to work out what is the expected behaviour for our current JMS Topic
          framework.
          I have a two server cluster with distributed topics configured. The two topics
          are configured to be durable. I have a test which generates about 100 events for
          test purposes. Under normal circumstances, each server processes about 50 messages.
          (Load balancing!)
          When the test is running, I kill one of the servers manually before it finishes.
          (Not a gracefull shutdown). The killed server processes about 20 messages, and
          the running server processes about 50. I can see that tables for the persistent
          topics have something (I don't know what) representing about all 100 events sent.
          When I bring the killed server back up, nothing happens. I would expect, from
          the documentation that I read, that the remaining 30 or so events will be put
          on the topic to be processed by our MDBs.
          Why don't all the events get placed on the topic of the killed server when it
          starts back up?
          What is the expected behaviour here?
          Is something wrong with my topic setup?
          Thanks in advance for any help...
          regards,
          Patrick Parato


Hi Patrick,
          Note 1: If you desire MDB to be transactional. Make sure
          the assembly descriptor in ejb-jar.xml is set to
          "Required" in addition to making the transaction-type
          "Container" as you have already done.
          <assembly-descriptor>
          <container-transaction>
          <method>
          <ejb-name>YOUREJBNAME</ejb-name>
          <method-name>onMessage()</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          </assembly-descriptor>
          Note 2: Your MDB is non-durable. It needs to be durable
          to cause messages to persist. Add the following line
          in the message-driven-destination clause of your ejb-jar.xml:
          <subscription-durability>Durable</subscription-durability>
          See the JMS FAQ on dev2dev.bea.com (or the JMS Performance
          Guide white-paper) for information on how to make
          sure a message is persistent.
          Note 3: Only one durable subscriber MDB will
          be able to attach to a given durable subscription, MDB's
          on other servers won't be able to, so even if the MDB
          is targeted at the cluster only one MDB will be able
          to process messages. This is the nature
          of durable subscriptions. I'm attaching some personal
          notes on the subject.
          Note 4: Durable subscriptions must refer to
          the JNDI name of member destinations, not to
          the distributed destination. WL does not support
          durable subscriptions directly on a distributed topic.
          Note 5: If you do not want message replication I'm not
          sure why you are using a distributed topic. Use a
          distributed queue.
          Tom
          Patrick Parato wrote:
          > Tom,
          >
          > Thanks for the quick reply.
          >
          > The first thing I want to clarify is that we only have one subscriber (MDB) that
          > is deployed once across multiple servers in a cluster. So this may explain why
          > each server is getting half the messages.
          Its still not clear. Each MDB pool should get each message.
          The individual
          instances in the pool will divide the messages sent to their MDB
          pool's subscription among them.
          >
          >
          >>2) Make sure that you are using durable subscribers. I suspect you
          >>are not. Note that durable subscribers are not supported
          >>for distributed destinations - they must refer directly to a member
          >>destination instead.
          >>
          >
          >
          > We are definitely using a distributed topic. The entry for our MDB in the weblogic-ejb.jar.xml
          > for the <destination-jndi-name> refers to the jndi name of the distributed topic.
          > So if I understand you correctly you are saying that the <destination-jndi-name>
          > should refer to the jndi name of an actual phyiscal topic on one of the servers.
          > By tying an MDB to a regular topic, how do we achieve failover if the JMS server
          > that the topic is associated with should fail?
          >
          >
          >
          > Here is a snippet of our config.xml:
          > (Names have been changed for security reasons)
          >
          > <JMSServer Name="JMS Server1" Store="Event Store1" Targets="myserver1">
          > <JMSTopic CreationTime="1065029382062"
          > JNDIName="distributed.topic@JMS Server1"
          > JNDINameReplicated="false"
          > Name="Distributed Topic@JMS Server1"
          > Template="Distributed Topic" TimeToDeliverOverride="5000"/>
          > </JMSServer>
          >
          > <JMSServer Name="JMS Server2" Store="Event Store2" Targets="myserver2">
          > <JMSTopic CreationTime="1065029382375"
          > JNDIName="distributed.topic@JMS Server2"
          > JNDINameReplicated="false"
          > Name="Distributed Topic@JMS Server2"
          > Template="Distributed Topic" TimeToDeliverOverride="5000"/>
          > </JMSServer>
          >
          >
          > <JMSDistributedTopic JNDIName="distributed.topic" Name="Distributed Topic" Targets="Cluster">
          > <JMSTemplate DeliveryModeOverride="Persistent"
          > Name="Distributed Topic" TimeToDeliverOverride="5000"/>
          > <JMSDistributedTopicMember
          > JMSTopic="distributed.topic@JMS Server1" Name="Distributed Topic@JMS
          > Server1"/>
          > <JMSDistributedTopicMember
          > JMSTopic="distributed.topic@JMS Server2" Name="Distributed Topic@JMS
          > Server2"/>
          > </JMSDistributedTopic>
          >
          >
          > ejb-jar.xml:
          >
          > <message-driven>
          >      <ejb-name>AnMDB</ejb-name>
          >      <ejb-class>package.AnMDB</ejb-class>
          >      <transaction-type>Container</transaction-type>
          >      <message-driven-destination>
          >           <destination-type>
          >                javax.jms.Topic
          >           </destination-type>
          >      </message-driven-destination>
          > </message-driven>
          >
          > weblogic-ejb.jar.xml:
          >
          > <weblogic-enterprise-bean>
          > <ejb-name>AnMDB</ejb-name>
          >      <message-driven-descriptor>
          >      <destination-jndi-name>distributed.topic</destination-jndi-name>
          >      </message-driven-descriptor>
          >      <enable-call-by-reference>True</enable-call-by-reference>
          >      <jndi-name>ejb.AnMDB</jndi-name>
          > </weblogic-enterprise-bean>
          >
          > Thanks for you help and quick reply.
          >
          > regards,
          > Patrick Parato
          >
          A durable topic subscriber MDB uses its name to generate its client-id.
          Since JMS enforces uniqueness on this client-id, this means that if a durable
          subscriber MDB is deployed to multiple servers only one server will be able
          to connect. Some applications want a different behavior where
          each MDB pool on each server gets its own durable subscription.
          The MDB durable subscription id, which must be unique on its topic, comes from:
          1) <jms-client-id>MyClientID</jms-client-id>
          (the weblogic dtd)
          2) if (1) is not set then the client-id
          comes from the ejb name.
          The durable subscription is uniquely identified within a cluster by a
          combination of "connection-id" and "subscription-id". Only one active
          connection may use a particular "connection-id" within a WebLogic cluster.
          The connection id comes from:
          1) The "ClientId" attribute configured on the WebLogic connection factory.
          This defaults to null. Note that if the ClientId is set on a connection
          factory, only one connection created by the factory
          may be active at a time.
          2) If (1) is not set, then, as with the subscriber-id,
          the connection-id is derived from jms-client-id descriptor attribute:
          <jms-client-id>MyClientID</jms-client-id>
          (the weblogic dtd)
          3) If (1) and (2) are not set, then, as with the subscriber-id,
          the connection-id is derived from the ejb name.
          Work-around:
          A) Create a custom connection-factory for each server:
          1) configure "JNDIName" to the same value across all servers
          ("myMDBCF" in this example)
          2) configure "ClientId" to a unique value per server
          3) enable "UserTransactionsEnabled"
          4) enable "XAConnectionFactoryEnabled"
          5) set "AcknowledgePolicy" to "ACKNOWLEDGE_PREVIOUS"
          6) target the CF at a single WebLogic server
          (Number 5 is required for non-transactional topic MDBs)
          B) In the MDB's weblogic-ejb-jar.xml descriptor, set the MDB's connection
          factory to the JNDI name of the custom connection factories configured in
          (A). Optionally, also specify the subscriber-id via the jms-client-id
          attribute.
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>exampleBean</ejb-name>
          <message-driven-descriptor>
          <connection-factory-jndi-name>myMDBCF</connection-factory-jndi-name>
          <jms-client-id>myClientID</jms-client-id>
          </message-driven-descriptor>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          C) Target the application at the same servers that have the custom connection
          factories targeted at them.
          Notes/Limitations:
          1) If the MDB is moved from one server to another, the MDB's corresponding
          connection-factory must be moved with it.
          2) This work-around will not work if the destination is not in the same
          cluster as the MDB. (The MDB can not use the local connection factory, which
          contains the connection-id, as connection factories do not work unless they
          are in the same cluster as the destination.)
          3) This work-around will not work for non-WebLogic JMS topics.

Distributed JMS help using topic - can it do this?

Using Weblogic 10.0, what is the a suggested configuration for having 2 apps in a cluster, where one creates messages in a distributed topic and another (a servlet) reads those messages? Messages need to be acknowleged and removed once read regardless of which managed server the user is on.
          Currently, I have a cluster of managed servers with a Uniform Distributed Topic, and I need a user to read a message just once regardless of which managed server he uses.
          I have 2 Ears - one creates messages, and another is a servlet that allows a user to read a message.
          My reader has a listener that subscribes on startup - like this:
          tconFactory.createTopicConnection(...);
          connection.createTopicSession(...)
          session.createSubscriber (...)
          It does a readNoWait() if a user clicks on a button. Another app puts messages in the topic.
          I want the user to read the message once (any only once) regardless of which managed server he is on.
          The way it is working is that if a user switches from one managed server to another he sees old messages he already read.
          Also, I tried using the module!queuename JNDI name but I get an exception. I have to just use the "regular" topic name.
          Any help appreciated!
          thanks in advance
          Edited by dantill at 05/16/2008 8:12 AM

So in a clustered environment, if a user is reading (and acknowledging) messages from a topic and that user is "load balanced" to another managed server on the cluster, he will see messages he already acknowledged?                     No - things don't work this way, unless the user is attaching to two different durable subscriptions. You may want to pick up a book on JMS, or study up on the Sun tutorials, and pay special attention to the difference between queues and topics, and the difference between "non-durable" and "durable" topic subscribers. It would likely help if you firmed up on these concepts before diving into the concept of distributed topics.
          The key points of WL distributed topics are:
          (1) Durable subscription can only be formed directly on a member (they can't move from member to member!), you can't specify the distributed topic JNDI name when creating a durable subscription - only the member JNDI name.
          (2) Non-durable subscriptions can specify the distributed topic JNDI name.
          (3) Just as with a non-distributed topic, every message that is sent to the distributed topic or that is sent directly to particular member is in turn delivered to every subscribers on every members.
          >>>> About Migratable targets - it may have been this statement:
          "A migratable target is a special target that can serve as a grouping of JMS services and which is active on only server member in a cluster."
          All this means is that multiple JMS services (such as JMS servers) can all target to the same MT. When the MT is migrated from one WL server to another, all related JMS servers are migrated.
          PS. Given my limited knowledge of your use case, it seems like you're looking for a distributed queue (not a topic), with a single consumer that can switch between one of two servers. Or perhaps one consumer on each server. In addition, in order to avoid "abandoning" messages on a particular queue member without consumers, there's a configurable option to have the idle member automatically forward its messages to a queue member that actually has consumers (queue forwarding option).
          Hope this helps,
          Tom

Weird things when persisting the jms messages of topic in the wls9?

I am testing the store of the jms messages in wls9.
          But when i sent a topic message to the topic, it seems that the message cannot be stored to the persistent stores.
          The things were that:
          when i send a message of queue and refreshed the page of console of wls9.I saw the number changed in :"Home > Summary of Persistent Stores > exampleJDBCStore "-Monitoring-Statistics,the "Create Count" had increased.
          But when i use the topic message, the "Create Count" never changed.
          Anybody can tell me why?
          Is the topic message cannot be stored in persistent stores, or others ?
          thx and rgds.

Topic messages are not persisted unless both the publisher qos is persistent and there are existing durable subscribers. Otherwise, there is no need to persist them. Do you have any durable subscribers?
          Tom

In ActionScript 2.0 , How can I send HTTP request and get the response in JSON format.

I am using ActionScript 2.0 for my app development. I have checked XML and LoadVars class. These classes by default send/receive data either in XML or name/value pair format. I want to send data in JSON format and receive the response in JSON format. How can I achieve this behavior using AS2.0. I have noticed that AS3.0 has the capabilities to do so. My client platform doesn't support AS3.0. Can anybody suggest a way to achieve this?
Thanks in Advance.

Atlast I am able to find the solution for this problem. In the end solutioin is very simple.
Following steps will help in sending request in JSON format.
1. extend LoadVars class
2. override toString method. (It should return JSON format )
3. Use subclass to send the request.

Propagate JMS Request Queue to JMS response in Topic

Similar Messages

Maybe you are looking for