Jms queue share

hi, i need some help relation to jms, recently i have a queue in clusterA but i need to share it with clusterB. The problem is that when i change the subdeployment and target to add the clusterB it says that the queue must be in one cluster. How can i resolve this to share it to the other cluster too?
Should i need to use sfa or bridge? Which would be the best to use in this case?
Thanks

Hi,
I was going through this thread and could understand that you have UDQ on cluster-1 (with 4 MS).. also you have 4 JMS-server mapped with 4 managed server instances. The producer application is deployed on cluster-1 which will send messages on UDQ.. which weblogic will distribute using the load balancing algorithms on the underlying JMS system i.e, to the 4 JMS server. Now I understand that you have another cluster-2 on same domain with 4 managed servers. Also cluster-2 hosts the consumer application to access the messages produced by producer. Your consumer application just need to create a JMS connection to the UDQ using connection factory config.. weblogic will itself map your 4 consumers (as app is deployed on cluster with 4 MS) to the 4 JMS servers of cluster1 . I don't see any requirement of pointing your UDQ to cluster-2. For type of consumer application to be used.. as already suggested by others it's best to use MDB which will be listening on all incoming messages on the queue.
As option 2 if you want to go with JMS bridge , then create 1 more UDQ to point it to cluster-2 (u will also require another JMS module which will point on cluster-2). The create a JMS bridge and add UDQ on cluster-1 as source destination and UDQ on cluster-2 as target destination. This way your application deployed on cluster-1 can put messages on source destination of JMS bridge and your say MDB application deployed on cluster-2 can access those messages over target destination of JMS bridge.
Hope this helps.
Thanks,
Ranjan

Similar Messages

Error while passing ODI variable in JNDI Url for JMS Queue XML

Hi,
Facing a weird problem while passing ODI variable in JNDI Url for JMS Queue XML.
Below is the JNDI Url configured under ODI Topology:
JNDI Url: t3://<host_location>?d=#TEST.SCHEMA_FILE&s=<schema_name>&JMS_DESTINATION=jms/<queue_name>
where,
#TEST.SCHEMA_FILE --> ODI variable storing xsd name and location
Issue Description:
If we restart ODI server then for the first run of any ODI interface using JMS Queue XML, it is unable to get the value for ODI variable present in JNDI Url (d=#TEST.SCHEMA_FILE).
It throws error message saying: No XSD found
Temporary Resolution:
As a temporary fix if we hard-code and pass the value in that ODI variable as shown below, it will successfully go through.
eg: JNDI Url: t3://<host_location>?d=C:\XSD\test.xsd&s=<schema_name>&JMS_DESTINATION=jms/<queue_name>
Reverting it back to variable later will have no issues and subsequent run will succeed.
But again anytime later if server is restarted then first run will have this issue.
Want to have permanent fix for it.
Any one having idea on it please share. Appreciate your help!

What ODI version are you using? It could be related to the bug in the older version as described in support note Doc ID 1290326.1

JMS queue consumer challenge

Hi there,
 I have met a pretty challenging problem in JMS queue consumer and
 would like to know if any JMS lovers in the group know about it.
 We have queue receiver listening on queue which contains a number of
 mugs.
 Once a msg is received (onMessage returns), the msg is handed over to
 a worker thread from a thread pool.
 Essentially there are two parts of the problem:
 1. We want kind of flow control - only x number of msg can be
 processed at a given time. This can be resolved by using semaphore.
 However, there might be better solution out there. Anyhow, this is
 less an issue than the second part -
 2. As we know client_acknowledge happens at the session level:
 Acknowledging a consumed message automatically acknowledges the
 receipt of all messages that have been consumed by its session. For
 example, if a message consumer consumes ten messages and then
 acknowledges the fifth message delivered, all ten messages are
 acknowledged.
 -- this is the problem -- we want to acknowledge each msg
 individually so that only the processed msg is acknowledged although
 there are x number of msg being retrieved. By doing that we won't lost
 any msg in case the JMS client crashes.
 It is a challenge, isn't it? Might well not be one for you, if you
 know the trick. If you do, could you share with us? Thanks a lot.
 Mike


Just to be clear, I favor (2), where each worker thread has its own session and
 consumer.
 This naturally throttles, as there are only as many outstanding messages as
 worker-threads.
 BTW, be aware that it is against spec, and dangerous, to call acknowledge()
 outside of
 onMessage() - as this multi-threads the Session and Session's are not thread
 safe.
 Tom
 Tom Barnes wrote:
 > Actually you both are correct. The ack behavior is configurable on the
 > connection factory via the "AcknowledgePolicy", where the default is
 > what the spec requires (ack-all). Prior to 6.1
 > the behavior was what one would expect (ack-before).
 >
 > As for how to solve the problem at hand. I can think of three approaches:
 >
 > (1) use the current async consumer but set the ack-policy
 > to ack-before, and defer acknowledging a msg until all msgs before
 > it have finished their processing
 >
 > (2) use multiple synchronous consumers, one consumer per defered msg
 >
 > (3) use a single synchronous consumer, but dequeue transactionally,
 > one transaction per msg. suspend the transaction, then have
 > the worker thread resume the transaction once it finishes processing
 > the message and call commit. (Take care that the default
 > tran timeout is 30 seconds.)
 >
 > Shean-Guang Chang wrote:
 >
 > > Just to correct one assumption. Ack the fifth message will not ack message
 > > received after that (e.g. message 6, 7, 8, etc...). At least not WLS JMS.
 > > If this is not true for you please give details of your client code and
 > > version of WLS JMS you have. Thanks!
 > >
 > > "Mike" <[email protected]> wrote in message
 > > news:[email protected]...
 > > > Hi there,
 > > >
 > > > I have met a pretty challenging problem in JMS queue consumer and
 > > > would like to know if any JMS lovers in the group know about it.
 > > >
 > > > We have queue receiver listening on queue which contains a number of
 > > > mugs.
 > > > Once a msg is received (onMessage returns), the msg is handed over to
 > > > a worker thread from a thread pool.
 > > >
 > > > Essentially there are two parts of the problem:
 > > >
 > > > 1. We want kind of flow control - only x number of msg can be
 > > > processed at a given time. This can be resolved by using semaphore.
 > > > However, there might be better solution out there. Anyhow, this is
 > > > less an issue than the second part -
 > > >
 > > > 2. As we know client_acknowledge happens at the session level:
 > > > Acknowledging a consumed message automatically acknowledges the
 > > > receipt of all messages that have been consumed by its session. For
 > > > example, if a message consumer consumes ten messages and then
 > > > acknowledges the fifth message delivered, all ten messages are
 > > > acknowledged.
 > > > -- this is the problem -- we want to acknowledge each msg
 > > > individually so that only the processed msg is acknowledged although
 > > > there are x number of msg being retrieved. By doing that we won't lost
 > > > any msg in case the JMS client crashes.
 > > >
 > > > It is a challenge, isn't it? Might well not be one for you, if you
 > > > know the trick. If you do, could you share with us? Thanks a lot.
 > > >
 > > > Mike

Distributed JMS Queues and Port Information

Hello,
          I am a reasonably inexperience WebLogic user, so forgive my ignorance.
          We are setting up a distributed JMS queue as a destination for messages being sent from our EAI server. The distribution will be across 2 servers in our QA environment and 3 servers in our production. We are using WebLogic Server 8.1.3 on an Windows 2003 environment.
          The people in our EAI environment need a port number on for the Queue in order to forward their messages to us. My question's are:
          1) Is the listen port for the Distributed Queue the same as the listen port for the Admin Server?
          2) If it is not, does it correspond to the listen port for the individual queues (which is the same between our environments)?
          3) If there is a third port in play, how does this get configured and where do I retreive this information?
          I appreciate any answers people are willing to give me on the issue.
          Thank you,
          Steven Enk
          Harley-Davidson Motor Company

Hi Steven,
          WebLogic JMS shares the same WebLogic port as other WebLogic services, regardless of whether or not the destinations are distributed.
          One way to determine which ports are configured for a particular WebLogic server is to look at the log for that server.
          Ports are usually configured to support multiple protocols, and typically, one uses the "t3" protocol for URLs (its the highest performer), but there are other options (such as "http" for tunneling).
          You can configure additional ports (beyond the "default" port(s)) using the "channel" feature - i think you can find channels under the "WebLogic server" tabs on the console.
          For a server or client to establish communication with a remote cluster, one need only specify a URL for any one of the server's within the remote cluster. J2EE JNDI name location transparancy and WebLogic RMI load balancing will usually take care of the rest, although some customers setup DNS to help with load balancing (by for example, configuing their DNS "round-robin" addresses).
          Best practice is for the administrative server to be restricted to administrative purposes only. This means the admin server typically (A) doesn't host JMS (or any other services or any applications) and (B) is not a member of a cluster. So typically you won't be able to access JMS using an admin server's URL.
          Tom

JMS/Queue cluster question

 Hi
 I have some very basic cluster questions on JMS Queues. Lets say Q1>I have 3 WLS
 in cluster. I create the queue in only WLS#1 - then all the other WLS (#2 and #3)
 should have a stub in their JNDI tree for the Queue which points to the Queue in
 #1 - right? Basically what I am trying to acheive is to have the queue in one server
 and all the other servers have a pointer to it - I beleive this is possible in WLS
 cluster - right??
 Q2> Is there any way a client to the queue running on a WLS can tell whether the
 Queue handle its using is local (ie in the same server) or remote. Is the API createQueue(./queuename)
 going to help here??
 Q3>Is there any way to create a Queue dynamically - I guess JMX is the answer -right?
 But I will take this question a bit further - lets say Q1 answer is yes. In this
 case if server #1 crashes - then #2 and #3 have no Queues. So if they try to create
 a replica of the Queue (as on server#1) - pointing to the same filestore - can they
 do it?? - I want only one of them to succed in creating the Queue and also the Queue
 should have all the data of the #1 Queue (1 to 1 replica).
 All I want is the concept of primary and secondary queue in a cluster. Go on using
 the primary queue - but if it fails use the 2ndry queue. Kind of HttpSession replication
 concept in clusters. My cluster purpose is more for failover rather than loadbalancing.
 TIA
 Anamitra


 Anamitra wrote:
 > Hi Tom
 > 7.0 is definitely an option for me. So lets take the scenarion on case of JMS cluster
 > and 7.0.
 >
 > I do not understand what u mean by HA framework?
 An HA framework is a third party product that can be used to automatically restart a failed server
 (perhaps on a new machine), and that will guarantee that the same server isn't started in two
 different places (that would be bad). There are few of these HA products, "Veritas" is one of
 them. Note that if you are using JMS file stores or transactions, both of which depend on the disk,
 you must make sure that the files are available on the new machine. One approach to this is to use
 what is known as a "dual-ported" disk.
 > If I am using a cluster of 3 WLS
 > 7.0 servers - as u have said I can create a distrubuted Queue with a fwd delay attribute
 > set to 0 if I have the consumer only in one server say server #1.
 > But still if the server #1 goes down u say that the Queues in server #2 and server
 > #3 will not have access to the messages which were stuck in the server #1 Queue when
 > it went down -right?
 Right, but is there a point in forwarding the messages to your consumer's destination if your
 application is down?
 If your application can tolerate it, you may wish to consider allowing multiple instances of it (one
 per physical destination). That way if something goes down, only those messages are out-of-business
 until the application comes back up...
 >
 >
 > Why cant the other servers see them - they all point to the same store right??
 > thanks
 > Anamitra
 >
 Again, multiple JMS servers can not share a store. Nor can multiple stores share a file. That will
 cause corruption. Multiple stores CAN share a database, but can't use the same tables in the
 database.
 Tom
 >
 > Tom Barnes <[email protected]> wrote:
 > >
 > >
 > >Anamitra wrote:
 > >
 > >> Hi
 > >> I have some very basic cluster questions on JMS Queues. Lets say Q1>I
 > >have 3 WLS
 > >> in cluster. I create the queue in only WLS#1 - then all the other WLS
 > >(#2 and #3)
 > >> should have a stub in their JNDI tree for the Queue which points to the
 > >Queue in
 > >> #1 - right?
 > >
 > >Its not a stub. But essentially right.
 > >
 > >> Basically what I am trying to acheive is to have the queue in one server
 > >> and all the other servers have a pointer to it - I beleive this is possible
 > >in WLS
 > >> cluster - right??
 > >
 > >Certainly.
 > >
 > >>
 > >> Q2> Is there any way a client to the queue running on a WLS can tell whether
 > >the
 > >> Queue handle its using is local (ie in the same server) or remote. Is
 > >the API createQueue(./queuename)
 > >> going to help here??
 > >
 > >That would do it. This returns the queue on the CF side of the established
 > >Connection.
 > >
 > >>
 > >> Q3>Is there any way to create a Queue dynamically - I guess JMX is the
 > >answer -right?
 > >> But I will take this question a bit further - lets say Q1 answer is yes.
 > >In this
 > >> case if server #1 crashes - then #2 and #3 have no Queues. So if they
 > >try to create
 > >> a replica of the Queue (as on server#1) - pointing to the same filestore
 > >- can they
 > >> do it??
 > >> - I want only one of them to succed in creating the Queue and also the
 > >Queue
 > >> should have all the data of the #1 Queue (1 to 1 replica).
 > >
 > >No. Not possible. Corruption city.
 > >Only one server may safely access a store at a time.
 > >If you have an HA framework that can ensure this atomicity fine, or are
 > >willing
 > >to ensure this manually then fine.
 > >
 > >>
 > >>
 > >> All I want is the concept of primary and secondary queue in a cluster.
 > >Go on using
 > >> the primary queue - but if it fails use the 2ndry queue. Kind of HttpSession
 > >replication
 > >> concept in clusters. My cluster purpose is more for failover rather than
 > >loadbalancing.
 > >
 > >If you use 7.0 you could use a distributed destination, with a high weight
 > >on the destination
 > >you want used most. Optionally, 7.0 will automatically forward messages
 > >from distr. dest
 > >members that have no consumers to those that do.
 > >
 > >In 6.1 you can emulate a distributed destination this way (from an upcoming
 > >white-paper):
 > >Approximating Distributed Queues in 6.1
 > >
 > >If you wish to distribute the destination across several servers in a cluster,
 > >use the distributed
 > >destination features built into WL 7.0. If 7.0 is not an option, you can
 > >still approximate a simple
 > >distributed destination when running JMS servers in a “single-tier”
 > configuration.
 > > Single-tier indicates
 > >that there is a local JMS server on each server that a connection factory
 > >is targeted at. Here is a
 > >typical scenario, where producers randomly pick which server and consequently
 > >which part of the
 > >distributed destination to produce to, while consumers in the form of MDBs
 > >are pinned to a particular
 > >destination and are replicated homogenously to all destinations:
 > >
 > >· Create JMS servers on multiple servers in the cluster. The servers will
 > >collectively host the
 > >distributed queue “A”. Remember, the JMS servers (and WL servers) must
 > >be named differently.
 > >
 > >· Configure a queue on each JMS server. These become the physical destinations
 > >that collectively become
 > >the distributed destination. Each destination should have the same name
 > >"A".
 > >
 > >· Configure each queue to have the same JNDI name “JNDI_A”, and also
 > take
 > >care to set the destination’s
 > >“JNDINameReplicated” parameter to false. The “JNDINameReplicated”
 > parameter
 > >is available in 7.0, 6.1SP3
 > >or later, or 6.1SP2 with patch CR061106.
 > >
 > >· Create a connection factory, and target it at all servers that have a
 > >JMS server with “A”.
 > >
 > >· Target the same MDB pool at each server that has a JMS server with destination
 > >“A”, configure its
 > >destination to be “JNDI_A”. Do not specify a connection factory URL
 > when
 > >configuring the MDB, as it can
 > >use the server’s default JNDI context that already contains the destination.
 > >
 > >· Producers look up the connection factory, create a connection, then a
 > >session as usual. Then producers
 > >look up the destination by calling javax.jms.QueueSession.createQueue(String).
 > > The parameter to
 > >createQueue requires a special syntax, the syntax is “./<queue name>”,
 > so
 > >“./A” works in this example.
 > >This will return a physical destination of the distributed destination that
 > >is local to the producer’s
 > >connection. This syntax is available on 7.0, 6.1SP3 or later, and 6.1SP2
 > >with patch CR072612.
 > >
 > >This design pattern allows for high availability, as if one server goes
 > >down, the distributed destination
 > >is still available and only the messages on that one server become unavailable.
 > > It also allows for high
 > >scalability as speedup is directly proportional to the number of servers
 > >on which the distributed
 > >destination is deployed.
 > >
 > >
 > >
 > >>
 > >> TIA
 > >> Anamitra
 > >
 > >
 > ><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 > ><html>
 > >Anamitra wrote:
 > ><blockquote TYPE=CITE>Hi
 > > I have some very basic cluster questions on JMS Queues. Lets say Q1>I
 > >have 3 WLS
 > > in cluster. I create the queue in only WLS#1 - then all the other WLS
 > >(#2 and #3)
 > > should have a stub in their JNDI tree for the Queue which points to
 > >the Queue in
 > > #1 - right?</blockquote>
 > >Its not a stub. But essentially right.
 > ><blockquote TYPE=CITE>Basically what I am trying to acheive is to have
 > >the queue in one server
 > > and all the other servers have a pointer to it - I beleive this is
 > >possible in WLS
 > > cluster - right??</blockquote>
 > >Certainly.
 > ><blockquote TYPE=CITE>
 > > Q2> Is there any way a client to the queue running on a WLS can tell
 > >whether the
 > > Queue handle its using is local (ie in the same server) or remote.
 > >Is the API createQueue(./queuename)
 > > going to help here??</blockquote>
 > >That would do it. This returns the queue on the
 > >CF side of the established Connection.
 > ><blockquote TYPE=CITE>
 > > Q3>Is there any way to create a Queue dynamically - I guess JMX is
 > >the answer -right?
 > > But I will take this question a bit further - lets say Q1 answer is
 > >yes. In this
 > > case if server #1 crashes - then #2 and #3 have no Queues. So if they
 > >try to create
 > > a replica of the Queue (as on server#1) - pointing to the same filestore
 > >- can they
 > > do it?? 
 > >- I want only one of them to succed in creating the Queue and also the
 > >Queue
 > > should have all the data of the #1 Queue (1 to 1 replica).</blockquote>
 > >No. Not possible. Corruption city.
 > > Only one server may safely access a store at a time.
 > > If you have an HA framework that can ensure this atomicity fine, or
 > >are willing
 > > to ensure this manually then fine.
 > ><blockquote TYPE=CITE>
 > >All I want is the concept of primary and secondary queue in a cluster.
 > >Go on using
 > > the primary queue - but if it fails use the 2ndry queue. Kind of HttpSession
 > >replication
 > > concept in clusters. My cluster purpose is more for failover rather
 > >than loadbalancing.</blockquote>
 > >If you use 7.0 you could use a distributed destination, with a high weight
 > >on the destination
 > > you want used most. Optionally, 7.0 will automatically
 > >forward messages from distr. dest
 > > members that have no consumers to those that do.
 > >In 6.1 you can emulate a distributed destination this way (from an
 > >upcoming white-paper):
 > > Approximating Distributed Queues in 6.1
 > >If you wish to distribute the destination across several servers
 > >in a cluster, use the distributed destination features built into WL 7.0.
 > >If 7.0 is not an option, you can still approximate a simple distributed
 > >destination when running JMS servers in a “single-tier” configuration.
 > >Single-tier indicates that there is a local JMS server on each server that
 > >a connection factory is targeted at. Here is a typical scenario,
 > >where producers randomly pick which server and consequently which part
 > >of the distributed destination to produce to, while consumers in the form
 > >of MDBs are pinned to a particular destination and are replicated homogenously
 > >to all destinations:
 > >· Create JMS servers on multiple servers in the cluster.
 > >The servers will collectively host the distributed queue “A”. Remember,
 > >the JMS servers (and WL servers) must be named differently.
 > >· Configure a queue on each JMS server. These become
 > >the physical destinations that collectively become the distributed destination.
 > >Each destination should have the same name "A".
 > >· Configure each queue to have the same JNDI name “JNDI_A”,
 > >and also take care to set the destination’s “JNDINameReplicated”
 > parameter
 > >to false. The “JNDINameReplicated” parameter is available in
 > >7.0, 6.1SP3 or later, or 6.1SP2 with patch CR061106.
 > >· Create a connection factory, and target it at all servers
 > >that have a JMS server with “A”.
 > >· Target the same MDB pool at each server that has a JMS server
 > >with destination “A”, configure its destination to be “JNDI_A”.
 > >Do not specify a connection factory URL when configuring the MDB, as it
 > >can use the server’s default JNDI context that already contains the destination.
 > >· Producers look up the connection factory, create a connection,
 > >then a session as usual. Then producers look up the destination by
 > >calling javax.jms.QueueSession.createQueue(String). The parameter
 > >to createQueue requires a special syntax, the syntax is “./<queue name>”,
 > >so “./A” works in this example. This will return a physical
 > >destination of the distributed destination that is local to the producer’s
 > >connection. This syntax is available on 7.0, 6.1SP3 or later,
 > >and 6.1SP2 with patch CR072612.
 > >This design pattern allows for high availability, as if one server
 > >goes down, the distributed destination is still available and only the
 > >messages on that one server become unavailable. It also allows
 > >for high scalability as speedup is directly proportional to the number
 > >of servers on which the distributed destination is deployed.
 > > 
 > > 
 > ><blockquote TYPE=CITE>
 > > TIA
 > > Anamitra</blockquote>
 > ></html>
 > >
 > >

Sending messages concurrently to JMS queue

Hi,
I am using Weblogic 10.3 JMS. I have a .NET producer sending messages to a JMS queue using a threadpool. A Java consumer will be consuming the messages. Is it possible to pool the conections/sessions from the producer side to send messages concurrently from the threadpool. Please help.

You can use standard .NET threading to produce messages in different threads.
Keep in mind that producers and session instances themselves must not be multi-threaded, although they can all share the same connection.
When you code, each thread could have a dedicated session and producer.
Alternately, you could write a very simple pool that the threads share to cache producers. On the other hand, sessions and producers are light-weight once they've been created, so there's often little need to go through this trouble.
Tom

I want to access JMS Queue in websphere from a client application

Hello all
I tried to access a jms queue in the websphere from a client application
my connection factory jndi name is : MyConn
my queue name jndi name is : MyQueue
and here is my code :
Hashtable environment = new Hashtable();
environment.put(Context.INITIAL_CONTEXT_FACTORY,
"com.ibm.websphere.naming.WsnInitialContextFactory");
environment.put(Context.URL_PKG_PREFIXES, "com.ibm.ws.naming");
environment.put(Context.PROVIDER_URL, "corbaloc:iiop:localhost:2809");
return new InitialContext(environment);
then:
q = (Queue) ctx.lookup(QJNDIName);
QueueConnectionFactory connFactory = (QueueConnectionFactory)
ctx.lookup(ConnFactName);
I had the following exception :
javax.naming.NameNotFoundException: Context: networking/nodes/networking/servers/server1, name: MyQueue: First component in name MyQueue not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
Can i have any help please ....

Hi
You are missing some critical jar files in your class path. It should be namingclient.jar, also please or something similar that is missing in classpath.
HTH
VJ

Oracle AQ to JMS Queue which is on Oracle Application server

Hi,
I am using Oracle Streams AQ Oracle database 10g
and i have a JMS Queue on oracle Application server.
how i can Propagate message from Oracle AQ (AQ$_JMS_TEXT_MESSAGE)Queue to JMS Queue. ?
Thanks,
Satnani

Hi Justin,
Thanks for Reply, but in my case my JMS queue is on Oracle Application Server.
and i want to propagate message from AQ to JMS queue.
and none of the document is available to describe how to send message from oracle database AQ to JMS queue which is on application server.
please help
Thanks,
Satnani

How to delete the messages from JMS Queue

Hi,Can anybody help how to delete the messages from the JMS Queue.Thanks in advance.

You can dequeue the message using a JMS client or delete it using Weblogic Admin Console -
http://download.oracle.com/docs/cd/E17904_01/apirefs.1111/e13952/taskhelp/jms_modules/queues/ManageQueues.html
Regards,
Anuj

How to read the messages in the JMS Queue using JMX

Hi,
          I want to read messages in the JMS queue using JMX. I was able to read using QueueBrowser but want to modify priority of the messages using JMX.
          I tried to use JMSDestinationRuntimeMBean but it does not allow us to read messages unless we pass the message Id. Is there any way that I can get all the messages in the queue.
          I am using Weblogic 8.1 SP4
          Can someone please help me in this regard.
          Thanks,
          Kiran.
          Edited by KGudipati at 10/22/2007 1:22 AM

Hi,
As far as i know, JMS Object Messages is not supported by XI JMS adapter.
you need to have the JMS provider to transform the message to bytes messages.
(Refer to SAP note 856346)

How to configure my JMS QUEUE serve only one message at a time?

Hi All,
I have requirement where I need to develope a JMS QUEUE in weblogic. This MDB has to serve only one message at a time. Is there any way to configure via annotations or in weblogic server settings ?
Any help would be really appreciated...
Thank you,
K.

I'm not aware of any way to configure the max pool size via annotations, you might try posting to the EJB newsgroup (please post back the answer). Of course you can set the size via an EJB descriptor, as per the MDB chapter of the Performance and Tuning guide in the edocs.
By the way, if you have ordered message processing requirements, I highly recommend taking a look at the WebLogic JMS "Unit-of-Order" (UOO) feature as per the UOO chapter of the JMS programmer's guide. For a variety of reasons, the UOO features is often, by far, the best option for handling such requirements. If this feature applies to your use case, then there would be no need to force single threaded message processing in some sort of manual fashion (the feature enforces this for you).
Tom

Dequeue from JMS Queue 10 at a time and process it.

Hi,
I have created a JMS queue in weblogic.
Say i enqueue 1000 records in the queue at one go.
Now, i want a bpel process to dequue from it and process it.
However as per my requirement i want at a time 10 instances being active at a time i.e. 10 records from the queue are being processed at a time.
Once any one of them finishes, the other will pick up the message.
1 BPEL instance will process only 1 record from Q at a time
Please let me know how to achieve this.

You need to understand here that it is adapter which deques the message from queue and it will deliver it to BPEL for processing which is an async process. So adapter will keep dequeing messages and keep publishing it to BPEL irrespective of whether BPEL process has completed processing.
You may need to tweak the adapter configuration here. First of all create the synchronous BPEL composite so that both adapter and BPEL work in same transaction -
https://blogs.oracle.com/adapters/entry/creating_a_synchronous_bpel_composite_using_file_adapter
You may control the number of threads for inbound JMS adapter using binding property "adapter.jms.receive.threads" in composite.xml
Regards,
Anuj

Multiple Messages in Same JMS queue

Hello,
I have interfaces in which different xml messages from the same sender system will be placed in the same MQ queue, is there a way that XI JMS sender channel can differentiate the xml messages based on the payload?
I can create a single communication channel, but the outbound message interface I cannot create a common structure because the xml messages are huge and there will be future interfaces following the same architecture.
1. How can I route in interface determination based on the context in the inbound msg interface?
2. What can I provide as Message interface for the outbound?
3. MessageSelector attribute in Adapter specific properties - any ideas on this? - I can select this in the condition context in interface determination - can I give any values here to differentiate msges?
4. Value mapping - is it possible to define the sender message interface through this?
Any idea is appreciated..THank you..

Hi Thanujja,
We have recently completed a project that had this requirement too. We made use of the MessageSelector to solve this problem. You'll need to make use of some advanced (advanced tab)settings in the comm channel. Basically you want to add Additional JMS Message Properties. You can add up to 10 additonal JMS Properties.
Let's say you've added a property called MESTYP. You then need to get the sender to populate the MESTYP property with a text value for each IDoc involved e.g. DELVRY. You would then set your JMS Message Selector field as follows: MESTYP='DELVRY'.
You'll have a comm channel for each IDoc. These comm channels will then connect to the JMS Queue & only pick up messages that meet the criteria at set in the Message Selector.
There was one other problem that encountered with Message Selector, we were on XI version 7.0, the Message Selector was working intermittently & then we applied SAP Note 1256636 & upgraded to 7.01. Everything is working fine after that.
Trevor

Reading Message from Foreign JMS Queue in SOA Suite 11g.

Hi,
I am trying to read a JMS message that has been put into a JMS Queue on a remote weblogic Server.
The steps that I know is that I need to create a foreign JMS Server and then probably use JMS Adapter to subscribe to the message that is lying in the remote queue.
Has anybody been able to achieve this kind of scenario working for a remote JMS queue? Also, is this supported by JMS Adapter in SOA11g?
Any help will be appreciated.
Regards,
Varun Maheshwari

Hi Atheek1,
Thanks for your reply.
The confusion that is pondering me is that do I need to create a Foreign JMS Server or should I create a JMS adapter and override the properties.
I have tried the steps for creating a Foreign Server from the below link
Unable to access remote JMS Queue through JMS Adapter
But I am not able to find the Foreign Server created and any connection factories and Destinations related to foreign Server in my JMS Destination while configuring JMS Adapter.
I am not sure how to do step2 as entailed by you.
Could you please explain me in little detail on how to do this or redirect me to some blog or forum which will be really helpful.
Cheers,
Varun

Reading Opaque data from jms queue and decoded in java embedding

Hi ,
Objective:Fetch text message from queue and print it from java embedding in BPEL
I am fetching text message from a jms queue using JMS adapter in BPEL.Then converting the opaque data(Base64 binary)to string using java embedding.My build got successful but I am getting runtime error at the time of deployment.
I have added fabric-runtime.jar file into SCA-INF\lib folder as well as project library directory.
<extensionActivity>
<bpelx:exec name="Java_Embedding1" version="1.5" language="java">
<bpelx:exec import="java.io.*"/>
<bpelx:exec import="oracle.soa.common.util.Base64Decoder"/>
<![CDATA[//Write your java code below e.g.
 System.out.println("Hello, World");
// String input = ((Element)getVariableData("Receive1_Consume_Message_InputVariable")).getTextContent();
// String inputName = (String)getVariableData("input");
String input = (String)getVariableData("Receive1_Consume_Message_InputVariable");
//Receive1_Consume_Message_InputVariable.opaque
 System.out.println("input:"+input);
 addAuditTrailEntry(input);
 Base64Decoder Decoder = new Base64Decoder();
 try {
 String decoded = Base64Decoder.decode(input);
 setVariableData("Variable_opaque_decoded",decoded);
 addAuditTrailEntry(decoded);
catch(UnsupportedEncodingException uee)
uee.printStackTrace();
}]]>
</bpelx:exec>
</extensionActivity>
Error:
Error deploying archive sca_JMSToDBInsert_rev1.0.jar to partition "default" on server AdminServer [http://localhost:7001]
HTTP error code returned [500]
Error message from server:
There was an error deploying the composite on AdminServer: Error occurred during deployment of component: BPELProcess1 to service engine: implementation.bpel, for composite: JMSToDBInsert: ORABPEL-05250
Error deploying BPEL suitcase.
error while attempting to deploy the BPEL component file "C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\AdminServer\dc\soa_0fb06e23-bac3-4753-aae9-0fc4b54b4dd1"; the exception reported is: java.lang.RuntimeException: failed to compile execlets of BPELProcess1
This error contained an exception thrown by the underlying deployment module.
Verify the exception trace in the log (with logging level set to debug mode).
Check server log for more details.
Error deploying archive sca_JMSToDBInsert_rev1.0.jar to partition "default" on server AdminServer [http://localhost:7001]
#### Deployment incomplete. ####
Error deploying archive file:/C:/SOA Suite/SOA_POC/Client2JMSapps/Client2JMSapps/JMSToDBInsert/deploy/sca_JMSToDBInsert_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Could you guys please help me regarding this?
Thanks & Regards,
Souvik
Edited by: Souvik Pal on Apr 16, 2012 9:40 PM

You probably want to try the SOA Suite forum for OSB questions.
SOA Suite
There is an excellent book also:
http://jeffdavies.org/
The documentation goes over the fundamentals, but the book will be better for step by step examples.

Jms queue share

Similar Messages

Maybe you are looking for