Queue vs Distributed queue

Hi Guys,
Could you please help me resolve some doubts on Regular Queue and Distributed Queues.
1. What is the basic Difference between regular q and distributed q.
2. Can we deploy the regular q on clustered weblogic, If yes, how will this be different from deploying a distributed q on cluster.
Regards

Hi,
Queue or Distributed Queue had same set of working design but only one difference is one queue is set for one pinned services where as Distributed queue is targeted to Cluster that means, One distirbuted queue can have multiple queue which are targeted to individual managed server or JMS server.
I hope you know difference between Uniform distributed queue and Distributed queue.
Uniform Distributed queue will created its own temporary queue destination on run time where as Distributed queue will required physical queue to assigned with in clustere.
Hope I address your query.
Regards,
Kal

Similar Messages

Message Listener Listening to only 1 queue in distributed queue setup!

Hi guys,
This may be the wrong place to place this post.
We created a message system with OSB proxies moving messages back and forth between distributed queues. After all this shuffling messages around, the messages end up in a distributed queue where a java client is waiting to pick up results. Our problem is, it's only reading one of the queues in this distributed queue.
The following is the code segment that waits for the message with a specific id:
public Message receiveMessage(String queueName, String messageId) throws FrameworkException {
BytesMessage bytesMessage = null;
if (null == queueSession) {
init();
try {
Queue receiveQueue = lookupQueue(queueName);
QueueReceiver queueReceiver = null;
String selector =null;
if (null == messageId) {
queueReceiver = queueSession.createReceiver(receiveQueue);
} else {
selector = "JMSCorrelationID = '" + messageId + "'";
queueReceiver = queueSession.createReceiver(receiveQueue, selector);
bytesMessage =(BytesMessage) queueReceiver.receive();
queueReceiver.close();
}catch{...
Will queueReceiver.receive() listen to every member in a distributed queue (spread across 2 managed servers in a cluster)?
Thanks alot

Yes, the uniform distributed queue should be available on all targeted servers, providing that the jms module has been targeted to all of the OSB servers, and that your java app ( .war file? ) is targeted to both.
You can stop the java application so that messages remain in the queue "long enough" for you to see them from within the WL console. Then you can shutdown nodes in your cluster individually, so conform that the message is truly being distributed. Then the issue is whether the java app is reading from the entire distributed queue instead of just one node.
When you use the monitoring tab on your queue, do you see a queue entry for each jms server ( each mgd server needs one )?
Or is the issue that the java client is only reading from one server?

Uniform Distributed Queue - Delay in handing over to listener

Hi,
We have cluster of two managed servers. We have two physical destinations (queues) configured as uniform distributed queues. With this setup we observed that when a message is put in to the uniform distributed queue, it takes a while before it hands of to the consumer (message driven bean). This we are observing every time a message is delivered. Is there a configuration that we are missing that is causing this behavior?
Thanks,

Here are the answers
How long is "a while"? How are you measuring the delay?
It is usually around 5 mins. We are measuring the delay using wall clock timings (We have debug statements in the consumer. That are getting printed after 5 mins).Does your config.xml or JMS Module configuration have a "time-to-deliver-override/TimeToDeliverOverride" configured on a destination, or a "default-time-to-deliver/DefaultTimeToDeliver" configured on a connection factory, or does your app use the "setJMSDeliveryTime" extension?
No. We have not overridden the any of these parameters. See below for jmsmodule.xmlDoes your sender or MDB app happen to have a "sleep( or wait(" encoded in it somewhere?
No. :-)Did you enable transaction batching on the MDB?
NoOr you hava you configured a batch delay somehow (this can happen if a SAF Agent or Bridge is in the flow)? No
Are you using Error Destinations?
No
jms-module.xml
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
<connection-factory name="inventoryWSQueueCF">
<sub-deployment-name>inv_jms_server</sub-deployment-name>
<jndi-name>inventoryWSQueueCF</jndi-name>
<transaction-params>
<xa-connection-factory-enabled>true</xa-connection-factory-enabled>
</transaction-params>
</connection-factory>
<connection-factory name="inventoryTPQueueCF">
<sub-deployment-name>inv_jms_server</sub-deployment-name>
<jndi-name>inventoryTPQueueCF</jndi-name>
<transaction-params>
<xa-connection-factory-enabled>true</xa-connection-factory-enabled>
</transaction-params>
</connection-factory>
<connection-factory name="inventoryWSQueueAlternateCF">
<sub-deployment-name>inv_jms_server</sub-deployment-name>
<jndi-name>inventoryWSQueueAlternateCF</jndi-name>
<transaction-params>
<xa-connection-factory-enabled>true</xa-connection-factory-enabled>
</transaction-params>
</connection-factory>
<uniform-distributed-queue name="inventoryWSQueue">
<sub-deployment-name>inv_jms_server</sub-deployment-name>
<jndi-name>inventoryWSQueue</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>10</forward-delay>
</uniform-distributed-queue>
<uniform-distributed-queue name="inventoryWSQueueAlternate">
<sub-deployment-name>inv_jms_server</sub-deployment-name>
<jndi-name>inventoryWSQueueAlternate</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>10</forward-delay>
</uniform-distributed-queue>
<uniform-distributed-queue name="inventoryTPQueue">
<sub-deployment-name>inv_jms_server</sub-deployment-name>
<jndi-name>inventoryTPQueue</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-queue>
</weblogic-jms>
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

How to process one message at a time on a distributed queue

I have a situation where I need to execute/process a task of a type
          asynchronously and this should be done one at a time. To do that I am thinking of setting
          up a distributed queue (for load balancing and failover). Now I have
          this requirement that only one task should be processed at one time. So
          for example if two messages (m1 followed by m2) are sent to distributed
          queue and I have the distributed queue which points to two physical
          queues on two different instances of weblogic(wl1 and wl2), the
          distributed queue will likely send m1 to wl1 and m2 to wl2 (assuming
          distributed queue is setup with round robin policy). If m1 has started
          executing/processing in my MDB on wl1, I do not want start processing
          m2 on wl2 untill m1 has been processed by wl1. Is it possible to do
          this on weblogic 8.1 JMS?
          If this is not supported I was thinking of implementing a database
          based locking framework and each mdb will use that framework to check
          if a task of a particular type is being processed before processing a
          new task. Also in this case I will need to use max. 1 mdb for each
          queue on each weblogic server.
          --Navjeet

Hello navjeet,
          I don't think there are any parameters that you can set on a distributed queue to ensure messages are handled in the sequential manner you describe so it looks like you will have to implement your own locking mechanism.
          In reposponse to your other question you can set the number of MDbeans in the free pool to 1 (or the number of queues you have) in the MDBean deployment descriptor.
          see:
          http://e-docs.bea.com/wls/docs81/ejb/message_beans.html#1120592
          Cheers,
          Hoos

Messages in Distributed Queue remain on one JMSServer in Cluster

Hi,
          the situation is as follows:
          We're having Distributed Queues on a two-Node server setup. A queue therefore exists two times, once on each JMSServer on each node.
          Forward-Delay has been set on the DistibutedQueue to value 1 second (we tested with values 0 and 10, too).
          External Java client (both cluster nodes in the provider_url for initialcontext) connects to the DistributedQueue and sends messages. In the weblogic console you can see these messages on the physical queue on the JMSServer, let's call it QueueA on NodeA.
          An external java process to consume messages (again both clusters nodes in the jndi-connection-string) is started to consume messages. Because of round-robin it sometimes get's connections to QueueB (part of same DistributedQueue as QueueA, but on the other node in the cluster).
          When connected to QueueB on NodeB no single message is received. You can even see in the weblogic console that QueueA on NodeA has zero consumers and 50 messages, QueueB on NodeB has zero messages but one consumer.
          When we restart the consumer java process and it randomly get's connected to QueueA on NodeA it consumes fine, as it should.
          Should'nt Forward-Delay do exactly this? Transport messages from QueueA on NodeA with zero consumers to QueueB on NodeB which actually has consumers?
          Any help would be appreciated.
          Axel van Lil

Hi,
          thanks for your answer. We opened a support case today for this issue... I don't know. Cluster seems to run fine, no warnings, no exceptions.
          The next step of this issue is the following (just to give an idea of our upcoming problems :-)
          External Java process listens on QueueA on NodeA (QueueA is part of a Distributed Queue). Currently receives all the messages located on that queue. We kill NodeA on that machine to simulate failover.
          The external process failovers immediately to NodeB (which is good! proven by netstat and debugger) but just doesn't receive messages even though there are messages in that queue! It seems that the new consumer is just being forgotten by the BEA server.
          I don't know... somehow our configuration is quirked... or the BEA implementation doesn't work at all...
          Rgds,
          Axel

Distributed queue usage with custom queue listeners in cluster

Hi,
Can someone help in solving the issue. We have a web application which will create consumers(threads in infinite loop) for an inbound queue(name comes from DB table) and after doing certain process result will be pushed to outbound queue(name comes from DB table).
When application runs in single managed server(without clustering) every thing works fine.
If I want to deploy the same application in two managed servers (with are under same cluster) which talks to same DB how to handle above scenario
1. Create 2 JMS servers one on each managed server(on different machines)
2. Create queue one for each JMS server
3. Create distributed queue and add above two queues as members of it
4. Create connection factory and target it to cluster
After creating above instrastructure(similar infrastructure will be created for inbound and outbound queue), can I use distributed queue JNDI name to create listeners(threads) to read messages? Or do I need to create listeners for each individual member in the distributed queue?
I know that while sending message to distributed queue, I can create sender on distributed queue and weblogic automatically takes care of sending the message to appropriate member in the DQ, but how it works for distributed queue?
Also, want to know how can I access distributed queue? For example, if managed server 1 is accessed by http://10.11.134.24:7001 and managed server 2 is accessed by http://10.11.134.25:7001. which URL I need use in JNDI context provider URL to access distributed queue? can I use any URL will it make any difference?
Generally for servlets/JSPs we create proxy server to access it through cluster, instead of directly using managed server URLs. But how it works for distributed queue?
Thanks
Santhosh
Edited by: user8676720 on Oct 4, 2011 8:35 AM

          Yes.
          It turns out that if replicate local queue jndi name in cluster is set to false
          the message did not get forward :(
          Dongbo Xiao <[email protected]> wrote:
          >Sorry, the attribute is ForwardDelay, not ForwardPolicy.
          >
          >Dongbo
          >
          >Dongbo Xiao wrote:
          >
          >> Hi Eran,
          >>
          >> Have you set up the ForwardPolicy for the Distributed Queue?
          >> By default, the ForwardPolicy is -1, which turns off the forwarding.
          >>
          >> Dongbo
          >>
          >> eran wrote:
          >>
          >> > Hello,
          >> > I have 2 nodes in cluster each one has a pinned JMS server with a
          >queue QueueA
          >> > and QueueA2
          >> > respectively both mebers in a distributed destination dist_queue.
          >> > There is a consumer on QueueA only (startup class).
          >> > In case of a message sent to QueueA2 a consumer is created for QueueA2
          >automaticly
          >> > (seen in the admin console) out of the blue, and the message do not
          >get forward
          >> > to QueueA where my consumer is listening.
          >> > Monitoring JMS connections of both servers shows only my consumers'
          >connection.
          >> > Our application depends on the forward feature.
          >> > Am I doing something wrong? any ideas?
          >> >
          >> > Thanks.
          >> > Eran
          >

Issue with Distributed Queue and WebLogic Clustering

Hi, When a message is received by distributed queue, MDB is processing the message on two managed servers. There seems to be issue with clustering and the physical queues present on both the managed servers are receving the message.
Our environment configuration details are as below:
One Web logic Cluster with 2 nodes (2 managed web logic servers).
One MDB deployed on the cluster listening to a queue with JNDI name “xng/jms/CODEventsQueue”
One Distributed queue with two members on the two nodes of the cluster, and with JNDI name “xng/jms/CODEventsQueue”
Two members of the distributed queue deployed on two JMS servers, which are separately deployed on each managed server .
And the distributed queue is deployed on the cluster.
Any help is appreciated.
Thanks
Sampath

It is not clear to me how you concluded that "both the managed servers are receiving the message". Did you monitor the queues' statistics, or did you see both MDB instances received the same message?
It looks like that you using a weighted distributed queue. Do the two physical queues that compose the distributed queue have their own JNDI names? If so, what are they?
Have you tried to use a uniform distributed queue and see if the same behavior shows up?
You can find more about uniform distributed destination at
http://edocs.bea.com/wls/docs103/jms/dds.html#wp1313713
BTW, which WebLogic Server releases are you using? Could you provide the distributed queue configuration?
Thanks,
Dongbo

MDB in a Cluster using Local JMS Queue (not distributed)

          Can I create a MDB that receives messages from a Local JMS Queue (created on each
          node) rather than a distributed queue?
          When I try to deploy such an MDB I get the following exception:
          weblogic.management.DeploymentException: Exception:weblogic.management.ApplicationException:
          activate failed for TestLocalMDBCluster Module: TestLocalMDBCluster Error: Exception
          activating module: EJBModule(TestLocalMDBCluster,status=PREPARED) Unable to deploy
          EJB: AsyncProcessor from TestLocalMDBCluster.jar: [EJB:011046]Unable to create
          EJBRuntimeMBean. javax.management.InstanceAlreadyExistsException: mydomain:ApplicationRuntime=Node2_TestLocalMDBCluster,EJBComponentRuntime=Node2_TestLocalMDBCluster_TestLocalMDBCluster,Location=Node2,Name=Node2_TestLocalMDBCluster_TestLocalMDBCluster_AsyncProcessor_jms/myserver,ServerRuntime=Node2,Type=MessageDrivenEJBRuntime
          at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
          at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:2371)
          at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:876)
          at weblogic.management.internal.RemoteMBeanServerImpl.private_registerMBean(RemoteMBeanServerImpl.java:582)
          at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanServerImpl.java:524)
          at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:166)
          at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:122)
          at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:85)
          at weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.<init>(EJBRuntimeMBeanImpl.java:33)
          at weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:30)
          at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.initPool(MessageDrivenBeanPoolInfoImpl.java:182)
          at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.activate(MessageDrivenBeanPoolInfoImpl.java:245)
          at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.activatePoolInfo(MessageDrivenBeanInfoImpl.java:474)
          at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanInfoImpl.java:440)
          at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1327) at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
          at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127)
          at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081)
          at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062)
          at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
          at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
          at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
          at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:608)
          at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          Is there any way to do this?


I assume you are using queues.
          I truly wonder what you are doing different. Since the
          error is occuring outside of JMS and in the EJB - before JMS is called -
          I suggest posting to the ejb newsgroup.
          Note that yours is a standard use case which distributed destinations
          are actually specifically designed for (if you
          are using customer connection factories, just
          make sure ServerAffinity is enabled on the connection factory to
          ensure that clients always connect to the local physical destination,
          configure the MDB to refer to the JNDI name of the distributed
          destination, and then target the MDB to the cluster - an MDB pool
          will then automatically be dedicated to each physical destination).
          Tom
          Mark Colwell wrote:
          > Nope. It happens every time we try the scenario no matter what the application
          > is or which cluster. It always happens if we try to deploy even just a single
          > MDB (no other beans in the jar) to a cluster where the queue specified in the
          > deployment descripter is a local queue created on each node in the cluster. When
          > the jar is deployed we get the error.
          >
          > We have a strange situation were we really need the queue to be local and not
          > distributed but existing on every node. We can create all the local queues no
          > problem but trying to then deploy the application goes boom.
          >
          > Thanks for the response!
          >
          > Cheers,
          > Mark
          >
          > Tom Barnes <[email protected].bea.com>
          > wrote:
          >
          >>Mark Colwell wrote:
          >>
          >>
          >>>Can I create a MDB that receives messages from a Local JMS Queue (created
          >>
          >>on each
          >>
          >>>node) rather than a distributed queue?
          >>
          >>Yes. In fact this is the most common use case.
          >>
          >>
          >>>When I try to deploy such an MDB I get the following exception:
          >>
          >>I don't recall seeing this exception before. It looks like a naming
          >>conflict - it appears that somehow something is already running with
          >>the same name. Are you somehow deploying the same app twice?
          >>
          >>javax.management.InstanceAlreadyExistsException:
          >>mydomain:ApplicationRuntime=Node2_TestLocalMDBCluster,
          >>EJBComponentRuntime=Node2_TestLocalMDBCluster_TestLocalMDBCluster,
          >>Location=Node2,
          >>Name=Node2_TestLocalMDBCluster_TestLocalMDBCluster_AsyncProcessor_jms/myserver,
          >>ServerRuntime=Node2,
          >>Type=MessageDrivenEJBRuntime
          >>
          >>FYI: As of one or two weeks ago, the MDB section of the
          >>EJB docs has been heavily updated. I highly recommend
          >>reading it.
          >>
          >>
          >>>weblogic.management.DeploymentException: Exception:weblogic.management.ApplicationException:
          >>>activate failed for TestLocalMDBCluster Module: TestLocalMDBCluster
          >>
          >>Error: Exception
          >>
          >>>activating module: EJBModule(TestLocalMDBCluster,status=PREPARED) Unable
          >>
          >>to deploy
          >>
          >>>EJB: AsyncProcessor from TestLocalMDBCluster.jar: [EJB:011046]Unable
          >>
          >>to create
          >>
          >>>EJBRuntimeMBean. javax.management.InstanceAlreadyExistsException: mydomain:ApplicationRuntime=Node2_TestLocalMDBCluster,EJBComponentRuntime=Node2_TestLocalMDBCluster_TestLocalMDBCluster,Location=Node2,Name=Node2_TestLocalMDBCluster_TestLocalMDBCluster_AsyncProcessor_jms/myserver,ServerRuntime=Node2,Type=MessageDrivenEJBRuntime
          >>>at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
          >>>at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:2371)
          >>>at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:876)
          >>>at weblogic.management.internal.RemoteMBeanServerImpl.private_registerMBean(RemoteMBeanServerImpl.java:582)
          >>>at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanServerImpl.java:524)
          >>>at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:166)
          >>>at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:122)
          >>>at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:85)
          >>>at weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.<init>(EJBRuntimeMBeanImpl.java:33)
          >>>at weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:30)
          >>>at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.initPool(MessageDrivenBeanPoolInfoImpl.java:182)
          >>>at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.activate(MessageDrivenBeanPoolInfoImpl.java:245)
          >>>at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.activatePoolInfo(MessageDrivenBeanInfoImpl.java:474)
          >>>at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanInfoImpl.java:440)
          >>>at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1327)
          >>
          >>at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
          >>
          >>>at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127)
          >>>at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081)
          >>>at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062)
          >>>at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
          >>>at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
          >>>at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
          >>>at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:608)
          >>>at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
          >>>at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at
          >>
          >>weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >>
          >>>Is there any way to do this?
          >>
          >

Message payload logging for Uniform Distribute Queue

Hi All,
We have a requirement to log the message payload, of every jms message received in a Uniform Distribute Queue in Weblogic.
Please let us know how can we achieve this.
Thanks.

If you want to avoid use of the Path Service, then the alternative is to make the destination members highly available. This will help ensure that the host member for a particular UOO is up.
One approach to HA is to configure "service migration". For more information see the Automatic Service Migration white-paper at
http://www.oracle.com/technology/products/weblogic/pdf/weblogic-automatic-service-migration-whitepaper.pdf
In addition, I recommend referencing Best Practices for JMS Beginners and Advanced Users
http://docs.oracle.com/cd/E17904_01/web.1111/e13738/best_practice.htm#JMSAD455 to help with WL configuration in general.
Hope this helps,
Tom

JMS Uniform Distribute Queue Unit Of Order, problem when one node goes down

Hi ,
I have the following code which post a message (with Unit of Order set ) to a Uniform Distribute Queue in a cluster with two member servers (server1 and server2).
--UDQ is targeted to a subdeployment that is mapped to two JMS servers pointing to each member servers
--Connection Factory is using default targeting ( i tried mapping to Sub deployment also)
javax.naming.InitialContext serverContext = new javax.naming.InitialContext();
javax.jms.QueueConnectionFactory qConnFactory = (javax.jms.QueueConnectionFactory)serverContext.lookup(jmsQConnFactoryName);
javax.jms.QueueConnection qConn = (javax.jms.QueueConnection)qConnFactory.createConnection();
javax.jms.QueueSession qSession = qConn.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
javax.jms.Queue q = ( javax.jms.Queue)serverContext.lookup(jmsQName);
weblogic.jms.extensions.WLMessageProducer qSender = (weblogic.jms.extensions.WLMessageProducer) qSession.createProducer(q);
qSender.setUnitOfOrder("MyUnitOfOrder");
javax.jms.ObjectMessage message = qSession.createObjectMessage();
HashMap<String, Object> map = new HashMap<String, Object>();
map.put("something", "SomeObject");
message.setObject(map);
qSender.send(message);
} catch (Exception e) {
Steps followed:
1. Post a message from "server1"
2. Message picked up by "server2"
3. Everything fine
4. Shutdown "server2"
5. Post a message from "server1"
6. ERROR: "hashed member of MyAppJMSModule!MyDistributedQ is MyAppJMSModule!MyJMSServer-2@MyDistributedQ which is not available"
WebLogic version : 10.3.5
Is there a way (other than configuring Path Service ) to make this code work "with unit of order" for a UDQ even if some member servers go down ?
Thanks very much for your time.

If you want to avoid use of the Path Service, then the alternative is to make the destination members highly available. This will help ensure that the host member for a particular UOO is up.
One approach to HA is to configure "service migration". For more information see the Automatic Service Migration white-paper at
http://www.oracle.com/technology/products/weblogic/pdf/weblogic-automatic-service-migration-whitepaper.pdf
In addition, I recommend referencing Best Practices for JMS Beginners and Advanced Users
http://docs.oracle.com/cd/E17904_01/web.1111/e13738/best_practice.htm#JMSAD455 to help with WL configuration in general.
Hope this helps,
Tom

Can distributed queues be implemented in weblogic 6.1

          hi,
          i am currently using weblogic 6.1 with 3 machines on a cluster.when using jms
          there seems to be no way to use distributed queues on the machine.this feature
          is however supported in weblogic 7.0.is there any workaround for this.this wuld
          essentially mean a single point of failure as the queue wuld be present on only
          1 wlserver and the other 2 servers though in cluster wuldnt have any reference
          to this queue..
          any help???


The JMS Performance Guide white-paper contains examples
          of doing exactly this. You can find it here:
          http://dev2dev.bea.com/technologies/jms/index.jsp
          Illusionz wrote:
          > hi,
          > i am currently using weblogic 6.1 with 3 machines on a cluster.when using jms
          > there seems to be no way to use distributed queues on the machine.this feature
          > is however supported in weblogic 7.0.is there any workaround for this.this wuld
          > essentially mean a single point of failure as the queue wuld be present on only
          > 1 wlserver and the other 2 servers though in cluster wuldnt have any reference
          > to this queue..
          > any help???

WebLogic 12.1.2 erases subdeployment on Distributed Queue when targeted to multiple JMS Servers

Update: verified in a 12.1.1.0 (JDK6) cluster - bug does not occur there.
Hi,
I have been migrating an 10.3.5.0 server to WebLogic 12.1.2.0 and have been unable to keep the subdeployment dropdown populated in the subdeployment tab of a uniform distributed queue when the subdeployment targets more than 1 JMS Server.
If I uncheck one of the servers - I work fine - however I would like to target all JMS Servers in the cluster - this used to work fine in 10.3.5.0
Following
http://docs.oracle.com/cd/E24329_01/apirefs.1211/e24401/taskhelp/jms_modules/distributed_queues/CreateUniformDistributedQueues.html
I am able to create a new queue no problem against the multiple-server subdeployment - but when I navigate to the subdeployment dropdown - the target is erased with "None".
If I save the subdeployment after setting it during the queue create - it is erased
<sub-deployment-name>MW-JMS-SubDeployment</sub-deployment-name>
Before:
<weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
<uniform-distributed-queue name="HousekeeperControlQueue">
    <sub-deployment-name>MW-JMS-SubDeployment</sub-deployment-name>
    <jndi-name>jms/HousekeeperControlQueue</jndi-name>
</uniform-distributed-queue>
</weblogic-jms>
After:
<weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
<uniform-distributed-queue name="HousekeeperControlQueue">
    <jndi-name>jms/HousekeeperControlQueue</jndi-name>
</uniform-distributed-queue>
</weblogic-jms>
Workaround:
- upon server startup the config is valid - just dont re-save the jms module or the subdeployment target will be erases
- also when creating a new subdeployment you will be able to select it from a jms distributed queue in the advanced targeting section even if it contains expected multiple JMS servers
- you will not however be able to edit the JMS queue once created - if there is any change to targeting - recreating the queue is required
thank you
/michael

Update: verified in a 12.1.1.0 (JDK6) cluster - bug does not occur there.
Hi,
I have been migrating an 10.3.5.0 server to WebLogic 12.1.2.0 and have been unable to keep the subdeployment dropdown populated in the subdeployment tab of a uniform distributed queue when the subdeployment targets more than 1 JMS Server.
If I uncheck one of the servers - I work fine - however I would like to target all JMS Servers in the cluster - this used to work fine in 10.3.5.0
Following
http://docs.oracle.com/cd/E24329_01/apirefs.1211/e24401/taskhelp/jms_modules/distributed_queues/CreateUniformDistributedQueues.html
I am able to create a new queue no problem against the multiple-server subdeployment - but when I navigate to the subdeployment dropdown - the target is erased with "None".
If I save the subdeployment after setting it during the queue create - it is erased
<sub-deployment-name>MW-JMS-SubDeployment</sub-deployment-name>
Before:
<weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
<uniform-distributed-queue name="HousekeeperControlQueue">
    <sub-deployment-name>MW-JMS-SubDeployment</sub-deployment-name>
    <jndi-name>jms/HousekeeperControlQueue</jndi-name>
</uniform-distributed-queue>
</weblogic-jms>
After:
<weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
<uniform-distributed-queue name="HousekeeperControlQueue">
    <jndi-name>jms/HousekeeperControlQueue</jndi-name>
</uniform-distributed-queue>
</weblogic-jms>
Workaround:
- upon server startup the config is valid - just dont re-save the jms module or the subdeployment target will be erases
- also when creating a new subdeployment you will be able to select it from a jms distributed queue in the advanced targeting section even if it contains expected multiple JMS servers
- you will not however be able to edit the JMS queue once created - if there is any change to targeting - recreating the queue is required
thank you
/michael

Looking up a distributed queue with two persistent stores using two JMS Svr

I am trying to do the following:
1. Setup a distributed queue, i have two servers which are part of the cluster:
Server A: t3://localhost:7003
Server B: t3://localhost:7005
I go in and create two jms servers:
JMS Server JA: Target on Server A
JMS Server JB: Target on Server B
Now as the jms servers need to use a seperate persistent store for each one of them i create two persistent stores.
2. Now from my MDB which is deployed on another server i lookup the queue using
t3://localhost:7003,localhost:7005 as the provider url
My problem is that i always end up listening to the messages on the first jms server and never get to read the messages on jms server JB as i guess i am able to connect to JMS Server JA so i never try and connect to JB? What to do about this?
Edited by: user4828945 on Mar 23, 2009 2:32 PM

Allocation of consumers wouldn't take into account the number of messages on the queue - they'd be allocated randomly. The scenario you're proposing shouldn't happen though - WebLogic Server takes into account whether a member has consumers when sending to a distributed destination, but otherwise, assuming that Queue 1 and Queue 2 both have consumers, then distribution of load will be equal. It's not the amount of consumers that determine how many messages get sent to a distributed destination member - it's whether it has members at all.
Assuming that did occur initially though, you'd expect processing to be a little bit more intensive on the server with the queue holding 30 messages. It would pretty quickly even up though.
From that point forward, it would be somewhere between difficult and impossible to get to the second scenario, where you have an unequal number of messages in each distributed destination member, unless the work being sent with each message to an MDB can vary significantly in how long it would take to process.
Assuming (and it's a big if) you could get to that scenario, then the MDBs wouldn't switch over - they stay connected to a particular distributed destination member. And it's their connection to a member as a consumer that controls how WebLogic Server load balances messages (assuming default configuration) so that's part of what makes it unlikely to get there.
From going back to first principles in the documentation, it seems like your best result would actually be from deploying the MDB to the cluster - that way, there's no remote connections to JMS queues, and you get a pool of MDBs on each server instance.
Ref here: http://e-docs.bea.com/wls/docs81/ejb/message_beans.html

Accessing Physical Queues in Distributed Environment

I am running WebLogic 10.3 in a cluster with 6 managed servers configured for Round Robin. I have a queue "OutEventQ" that is Uniform Distributed across the cluster.
I am trying to connect to the queue from Stand Alone WebLogic Message Driven EJB's that exist outside of the clustered environment. I have six of these Beans. I want each Bean to connect to a unique queue so that each queue in the cluster has a consumer. When I try and connect using the queue name alone, the connections sometimes go to a queue with no consumers and sometimes go to a queue that already has a consumer and I have to go through the process of killing the process and starting it again in a hit-or-miss fashion.
Is there a way to specify that each one of my Beans connects to a unique queue?
I have tried to connect using the syntax "OutEventQModule!JMS Server 1/OutEventQ" (i.e. "myModule!myServer/myQueue"), but that does not work. I have also tried variations where I use an @ symbol rather than the "/", but also this did not work either.

Hi,
* First of all, it is generally not a good practice for a JEE application that is running on a JEE server to consume messages with anything other than an MDB. There are a variety of reasons for this.
* By far the easiest and most highly recommended way to ensure full consumer coverage of a distributed queue is to use a WebLogic MDB as the consumer. The WebLogic MDB code will automatically ensure that all distributed queue members are serviced by a consumer even if the distributed queue is in a different cluster.
* A work-around that works for some customers is to enable "queue forwarding" in the distributed queue. Messages that are idled on a queue member without consumers will be automatically forwarded to queue members that do have consumers. This is not compatible with the "Unit-of-Order" feature, and it also has performance implications.
* If the above options don't apply to your use case, perhaps the next easiest way is to code your clients to periodically close and re-create their javax.jms.Consumer objects in order to force them to rebalance. This will help handle the case when a queue member starts up after all consumers have already pinned themselves to a member.
* If you still think that you have a need to lookup individual queue members, then the best way is simply to lookup the JNDI name of the member. The JNDI name of a uniform distributed queue member is "jms-server-name@udd-jndi-name". Since the JNDI option is straight-forward, and the syntax is simpler, I would not normally recommend using "session.createQueue()" methods to find a destination.
* Please post any future JMS related questions in the WebLogic JMS newsgroup.
Regards,
Tom Barnes
WebLogic JMS Developer Team
PS Hopefully relatively soon, most of the above information will be consolidated into either the JMS chapter of the Performance and Tuning guide in the documentation or a new "How to lookup a destination" chapter of the JMS Programmer's guide.
Edited by: TomB on Oct 12, 2009 2:31 PM
Edited by: TomB on Oct 12, 2009 2:33 PM

OSB 11g: Business Service not getting reply back from distributed queue

Here is the scenario:
OSB Domain A has a Business service that does a JMS send to a distributed JMS queue hosted on another WLS domain.
It expects a response from a distributed queue sitting on this same remote WLS domain.
The remote WLS domain is configured as a Foreign JNDI Provider in the OSB Domain with the request and response queues defined. Testing this business service, we see that messages are being posted to the remote request queue fine, and that the message are being picked up and processed. The response was sent to the response queue, but the message just sits there, the OSB business service did not pick it up. I can see 16 active Consumers on the response queue, presumably from the OSB business service?
Using CorrelationID.
URI for request/response queues are using the locally defined JNDI name for the queues and connection factories from the Foreign JNDI Provider definition:
- URI for request queue: jms:///[RemoteXAConnectionFactoryX]/[LocalJNDINameForRequestQueue]
- URI for response queue: jms:///[RemoteXAConnectionFactoryX]/[LocalJNDINameForResponseQueue]
Completely stumped at the moment...anybody has any ideas?
Thanks,
Melvin

Hi,
I am also facing the similar kind of issue as below. After placing the message in to request Queue, I need that message Id as response to that Business service. Please provide the solution for the below issue. Thanks in advance.
Thanks,
bharath.

Queue vs Distributed queue

Similar Messages

Maybe you are looking for