GetMembers from a distributed Queue/Topic

Hi,
          i don't know if i can get the members of a distributed queue or topic.
          I know the jndi of the distributed queue/topic, but i want to access the members directly. And i supose i can do it "dinamically", but i don't know how.
          any help ? i am lost.
          thanks

Hi,
          I assume you are talking about pre-9x "weighted" distributed destinations and yes you can use "getMembers()" from weblogic.management.configuration.JMSDistributeQueueMBean/JMSDistributedTopicMBean. You can also use specific getters such as getJMSDistributedQueueMembers()/TopicMembers()as well.
          In 9x, we only support the specific ones (getDistributedQueueMembers()/TopicMembers()) that are available from weblogic.j2ee.descriptor.wl.DistributedQueueBean/DistributedTopicBean API.
          Note that in 9x, we do have "uniform" distributed destination (UDD) that have their members managed internally and hence no accessors to get them. Another difference is that in 9x the configuration is represented by the "descriptior beans" as opposed to in pre-9x where we used to have JMX MBeans.
          For 9x, please take a look at weblogic.jms.extensions.JMSModuleHelper to get more info on the helper APIs.
          Hope this helps.
          Kats

Similar Messages

Reading messages from all distributed queues on a cluster (WLS 9.2)

Hi,
I have a following problem with distributed queues on WebLogic Server 9.2 MP1.
Here's a brief description of my setup:
I've got a cluster called 'myCluster', and two cluster nodes on it, 'nodeA' and 'nodeB'. I also have two JMS servers, 'jmsA' and 'jmsB'. Then I have a jms module 'myModule' with a subdeployment 'mySubdeployment' targeted on jms servers 'jmsA' and 'jmsB'. I have a jms connection factory 'TestFactory' that is targeted on myCluster (default targetting), and a jms queue 'TestQueue' (Uniform Distributed Queue) using subdeployment 'mySubdeployment' (targeted to 'jmsA' and 'jmsB').
Now, the queue 'TestQueue' is used as a location where messages are stored when the system has met a problem in the environment that is preventing the normal handling of messages. Messages are kept in this queue until the problem is over, that's when the system administrator uses a browser application that requests the system to read the messages and handle them normally.
The problem is that the cluster node which gets the request seems to be able to read only its own queue and the messages on the other nodes queue are left untouched. I know that I could send a message to the another node for example via topic 'purge_your_messages', but that's not suitable for this case. I need to sort the messages by their ids (set as a message property) and because of that I need exactly one node executing the purge.
Any advice?
- jj
Edited by: user5736915 on 10-Dec-2008 14:10

Browsers and receivers always attach to a single member of a distributed destination.
WebLogic MDBs, on the other hand, automatically handle the task of attaching receivers to every member, and are quite simple to code and use these days. If you have the option of using WL MDBs, I recommend using them. (There's no equivalent for browsers.)
Spring won't do the same OOTB, but there does appear to be a work-around for the Spring receiver issue (albeit not for browsers - just receivers). Here's a sample Spring impl that attaches a subscription to each and every member of a distributed topic:
http://sleeplessinslc.blogspot.com/2011/12/weblogic-jms-partitioned-distributed.html.
If the above isn't helpful, and you must cycle through every message on every server in the cluster, then you'll need write special case code to check each separately. There are two common options for enumerating the destinations and working with each one - the JMX mbean "message management" APIs (WLST Jython scripting or Java based) and the weblogic.jms.extensions destination availability APIs.
HTH,
Tom

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.

Redirecting failed messages to other consumers of distributed queue

Hi,
We have a simple cluster with two servers A and B, each hosting one MDB whose task is to consume message from a distributed queue and forward them to an EIS via a JCA resource adapter. Server B acts as a failover server. If the resource adapter is unable to deliver the message, the MDB will throw a runtime exception and the message will therefore be redelivered. In order to achieve high-availability, we have configured the distributed queue to send the redelivered message to an error destination (dead-letter-queue DLQ). The DLQ again has another instance of the MDB as a consumer with a different resource adapter.
Using DLQs is working fine as a high-availability mechanism when the MDB is unable to deliver the message to the EIS, but is this a common or valid approach?
An alternative to using DLQs would be to configure weblogic to send redelivered message to other consumers on the distributed queue. The problem we have is that the failed message always gets redelivered to the same MDB (i.e. the MDB which consumes messages but throws an exception because the resource adapter fails). Is it somehow possible to configure the MDB or even change the MDB code to notify weblogic to send the failed message to another consumer of the distributed queue? Would the MDB be able to disconnect the JMS connection when throwing the exception and if so, would the disconnection cause the application server to deliver the message to another consumer?
Many thanks

Thanks Tom,
Setting the distributed-destination-connection property to EveryMember seems to be exactly what we need to allow other distributed queue member to consume the message which has been put back on the queue after a rollback. In order to ensure that it won't be the same MDB consuming the failed message again, we would have to temporarily suspend the MDB. From what I read, one approach is to sleep the MDB after throwing the runtime exception (but is this possible, i.e. is it not going to interrupt the onMessage before going to sleep?). I also read that there is a new property from WLS 9.0 onwards to automatically stop the MDB for a certain time after an exception has ocurred, how can I configure this? Are we also going to have to set the MDB pool size to 1 in order to ensure that the message gets consumed by an MDB on a different server?
We have also tried to use a non-collocated approach instead using a collocated approach with distributed queues but we end up with the same problem that a message does not get redelivered to MDBs on other servers after a runtime exception has been thrown.
Thanks a lot

Consumers for distributed queues -- writing the JMS API

Hi,
I have Created a cluster MS_01 and MS_02.
JmsServer-MS01 for MS_01 and JmsServer-MS02 for MS_02.
Also have create a distributed queue called DistributedQueue-0 and a distributed connection factory called ConnectionFactory-0.
I have been successfully able to loadbalance sending of messages using the cluster address.
When i try to consume messages the consumers gets pinned to a MS_01. (As expected)
I am looking for ways where in using JMS API i can read messages from both the manages instances.
Appreciate any help.
thanking you all in advance.
Regards
Girish Subbaramu.

Hi,
For consuming messages from a distributed queue, by far the best option is to use a WebLogic MDB, which has internal code designed to work well with WebLogic distributed destinations. When a distributed queue runs in the same cluster as the MDB, the MDB service will ensure that there's an MDB deployment instance that is locally servicing each queue member -- even when the queue members migrate between servers, or when they are added or removed due to configuration changes. When the MDB is communicating with a distributed queue in a remote cluster, an MDB running on a single server will automatically set up consumers for each remote member and will dynamically react to member up/down add/remove events.
If you must use a straight javax.jms client, then I think there are two basic options. The first option is to ensure that that there are more than enough consumers to provide full coverage, and periodically close and re-open the consumers. The periodic close and re-open forces the consumers to load-balance again, and therefore helps handle the case when new destination members become available after the consumers have all attached. The second option is to create consumers directly on each member rather than on the distributed queues logical name (each member has a unique name that's advertised in JNDI).
Hope this helps,
Tom

Accessing Distributed Queue In a Cluster via the Proxy Server

          I am running WL 8.1 SP2. I have a configuration where I have 3 servers (on two
          different machines) running in a cluster. I have a separate server on a 3rd machine
          running the cluster proxy server for a single point of access to the cluster.
          I have configured a distributed queue and a distributed topic, each targeted
          to all servers in the cluster.
          Now I have a JMS client which is a separate java application that is trying to
          connect to the distributed queue and topic in the cluster. If the client connects
          directly to one of the cluster machines, it is able to successfully interact with
          the JMS queue and topic. But if it attempts to connect via the proxy server it
          gets an error saying the queue and topic does not exist.
          So what am I missing? Do I need to configure a separate JMS server on the proxy
          server and add that as part of the distributed queue & topic (this didn't seem
          to allow me to add anything outside of the cluster). Is there any special configuration
          in the proxy to pass through JMS requests? I'm currently using a WL logic server
          as my front-end proxy server but does anything change if I want to use Apache
          with the WL Proxy plug-in??
          Jerald


          "Jerald Pratt" <[email protected]> wrote in message
          news:[email protected]...
          >
          > I am running WL 8.1 SP2. I have a configuration where I have 3 servers
          (on two
          > different machines) running in a cluster. I have a separate server on a
          3rd machine
          > running the cluster proxy server for a single point of access to the
          cluster.
          > I have configured a distributed queue and a distributed topic, each
          targeted
          > to all servers in the cluster.
          >
          > Now I have a JMS client which is a separate java application that is
          trying to
          > connect to the distributed queue and topic in the cluster. If the client
          connects
          > directly to one of the cluster machines, it is able to successfully
          interact with
          > the JMS queue and topic. But if it attempts to connect via the proxy
          server it
          > gets an error saying the queue and topic does not exist.
          Yup... That makes sense...
          >
          > So what am I missing? Do I need to configure a separate JMS server on the
          proxy
          > server and add that as part of the distributed queue & topic (this didn't
          seem
          > to allow me to add anything outside of the cluster). Is there any special
          configuration
          > in the proxy to pass through JMS requests? I'm currently using a WL logic
          server
          > as my front-end proxy server but does anything change if I want to use
          Apache
          > with the WL Proxy plug-in??
          One option I have used frequenly is specifying java.naming.provider.url as
          cluster address (e.g. t3://server1:7001,server2:7001
          You may also want to look into tunnelling...
          >
          > Jerald
          >

Drop jms messages from distributed queue

hello
i am searching info for making one script (wlst?) for deleting messages from one jms distributed queue and i dont find it.
can you help me?
thanks

You can use the wlst scripts described in How to list total number of message in specific Topic/queue using wlst comm to find the right destination runtime MBean. Then call deleteMessages('true') on the destination runtime MBean. The method deleteMesages() takes a selector expression.
Hope this helps.
Dongbo
Edited by: Dongbo on Mar 14, 2012 10:44 AM

How to send BusinessEvent from oracle EBS 12 to an external JMS Queue/Topic

Hello Sir:
How to send BusinessEvent from oracle EBS 12 to an external JMS Queue/Topic??
How to receive BusinessEvent from an external JMS Queue/Topic to oracle EBS 12 ??
It is a Third Party JMS Server, it has queue and topic etc??
which module should be used??
what is the basic steps to do??
Thanks

swapnil_yeole wrote:
Hello,
We want to install Oracle EBS 12.1.1.
Our internet speed is very poor so it would not be feasible for us to download the software from E-delivery site.
Can you please let me know how & where to obtain Oracle EBS 12.1.1 DVD's.
Do we need to raise an SR with Oracle for same.
Thanks in advance.
Yes -- https://blogs.oracle.com/stevenChan/entry/how_to_obtain_media_packs
Thanks,
Hussein

JMS distributed queue on response

I have an ALSB business service sending requests to a distributed JMS queue and getting a response back from a distributed JMS queue using the correlation ID correlation pattern.
This approach seems to work just fine in my tests, but the ALSB documentation seems to indicate I must use the MessageID correlation pattern when using distributed queues.
My other coworkers seem to think this technique wont work as volumes increase. They say the business service is actually "pinned" to a specific physical response queue member in the distributed queue. If responses happen to go to a different member, the business service wont pick up the response.
Question: Is this a supported technique?
If not, is it correct to say one might use distributed queues for requests but should always specify physical queues for the response?

If you refer to distributed queue for topic based messaging, then correlationId is the right approach. If you are using a clustered JMS server, messageId is the right approach.
Gregory Haardt
ALSB Prg. Manager
[email protected]

JMS Server on a cluster stores all msgs posted to Distributed Queue on 1 server failure

          Hi
          I have a Cluster setup with 2 managed servers srvr1 & srvr2 each running its own
          JMS server.
          Product version in use is Weblogic SP2.
          Configured a Distributed Queue and deployed it on both the JMS servers.
          Set the load-balancing to round-Robin and Server-Affinity to False on the connection
          factory.
          The producer is an external client which posts 100 messages to the Distributed
          queue.
          Consumers are MDBs pinned to the respective physical queues on the respective
          JMS servers.
          Each server has its own store.
          Once 100 messages are posted to the Distributed Queue. The messages are distributed
          to
          the 2 Physical Destinations equally i.e 50-50 each.
          While the MDBs are processing the msgs, server srvr1 is brought down at a point
          when it has consumed only 10 of its 50 msgs.
          When the srvr1 is brought up again, i am finding that the store for that JMS server
          contains the 40 unprocessed msgs in its physical queue + the msgs on the other
          queue that were unprocessed at the time this server crashed.
          When srvr1 went down, srvr2 was running and it went on to process all its 50 msgs
          completly. Why would those processed msgs show up again when srvr1 is brought
          up ?
          Please provide some input !!
          Ravi.


          The log message is from the distributed destination
          "forwarders". In distributed queues, these forwarders
          automatically move messages from queues without
          consumers to queues that have them (queue
          forwarders are disabled by default). In distributed topics,
          the forwarders serve
          to replicate a published message from the local
          topic member to each of the remote topic members.
          "Raviprasad Athivilli" <[email protected]> wrote:
          >
          >Tom
          >
          >I think you are right. When the server1 is brought up again, its picking
          >up all
          >the messages
          >that were written to the store.
          >
          >But as it starts processing them, i get this exception on the server2
          >that has
          >been running from the beginning.
          >
          ><Oct 10, 2003 6:20:19 PM EDT> <Error> <JMS> <040366> <JMS Distributed
          >Destination
          >member "MyQueue@JMSServer-02" in "MyQueue"
          >unable to accept connection from remote member "MyQueue@JMSServer-01"
          >due to exception
          >weblogic.jms.common.JMSException: can't find
          >queue target jndi table for MyQueue@JMSServer-01 != MyQueue
          >weblogic.jms.common.JMSException: can't find queue target jndi table
          >for MyQueue@JMSServer-01
          >!= MyQueue
          > at weblogic.jms.backend.BEDestination.setupSystemSubscription(BEDestination.java:3466)
          > at weblogic.jms.backend.BEManager.sessionAndTopicSubscriberCreate(BEManager.java:234)
          > at weblogic.jms.backend.BEManager.invoke(BEManager.java:384)
          > at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:602)
          > at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:152)
          > at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsyncFuture(DispatcherImpl.java:396)
          > at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
          >Source)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
          > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
          > at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:821)
          > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
          > at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          >
          >What does this mean ?
          >
          >Ravi.
          >Tom Barnes <[email protected]> wrote:
          >>Seems more than odd. Are you sure that q1 got unprocessed
          >>messages from q2? How did you confirm?
          >>
          >>Perhaps q1 got messages its MDB already processed back again -
          >>an indication that the MDB is throwing Runtime exceptions
          >>or Errors, and the container is rolling back transactions.
          >>
          >>Raviprasad Athivilli wrote:
          >>> Hi
          >>>
          >>> I have a Cluster setup with 2 managed servers srvr1 & srvr2 each running
          >>its own
          >>> JMS server.
          >>> Product version in use is Weblogic SP2.
          >>> Configured a Distributed Queue and deployed it on both the JMS servers.
          >>> Set the load-balancing to round-Robin and Server-Affinity to False
          >>on the connection
          >>> factory.
          >>>
          >>> The producer is an external client which posts 100 messages to the
          >>Distributed
          >>> queue.
          >>> Consumers are MDBs pinned to the respective physical queues on the
          >>respective
          >>> JMS servers.
          >>> Each server has its own store.
          >>>
          >>> Once 100 messages are posted to the Distributed Queue. The messages
          >>are distributed
          >>> to
          >>> the 2 Physical Destinations equally i.e 50-50 each.
          >>>
          >>> While the MDBs are processing the msgs, server srvr1 is brought down
          >>at a point
          >>> when it has consumed only 10 of its 50 msgs.
          >>>
          >>> When the srvr1 is brought up again, i am finding that the store for
          >>that JMS server
          >>> contains the 40 unprocessed msgs in its physical queue + the msgs
          >on
          >>the other
          >>> queue that were unprocessed at the time this server crashed.
          >>>
          >>> When srvr1 went down, srvr2 was running and it went on to process
          >all
          >>its 50 msgs
          >>> completly. Why would those processed msgs show up again when srvr1
          >>is brought
          >>> up ?
          >>>
          >>> Please provide some input !!
          >>>
          >>> Ravi.
          >>
          >

Regarding JMS-Queue/Topic in Proxy and Business service in OSB

Hi
I have one query regarding to the JMS-Queue/Topic.
I am published the message to the JMS-Queue/Topic.
----My Business-service configuration is---
General----Any xml
Tranport--jms://localhost:7001/MyConnectionFactory/RequestQueue
Response--None
I call this Business-service in proxy-service of Routing message was published successfully to thee Queue.
I try to dequeue the message from that queue for this
--- I take another proxy with---
General----Any xml
Tranport--jms://localhost:7001/MyConnectionFactory/RequestQueue
In meassage flow
Routing--second busines-service)
--- Second business-service configuration is---
General----Any xml
Tranport-File (C://temp)
Issue is when I publish the message to Queue,the message is also found in the file i.e C:temp. I don't now why this come to the file.*
Any suggestions
Thanks
Mani

Either I did not get an idea, but in your JMS proxy you are routing to File :)
If you don't want file, why route to 2nd BS ?

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
          >

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

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

GetMembers from a distributed Queue/Topic

Similar Messages

Maybe you are looking for