Distributed Destination in WL 6.1SP5

Hi ,
          I am using WL6.1SP5 and implementing a JMS module where
          Messages needs to be delievered to all the Servers in the Cluster.
          This can be easily achieved in Weblogic 7 using Distributed Destination. However Dist. Dest. is not built in feature of WL6.1.
          IS there any way by which I can publish a message on ALL servers in a Cluster without implementing a Distributed Destination ?
          Thanks for the help in advance,
          Regards
          John

The first thing to realize is that a distributed destination is not required to make a JMS server's messages universally available on the cluster. Any messages on any JMS server in the cluster are transparently accessable from any other server in the cluster - they are location transparent.
What distributed destinations provide is "high availability" and "scalability". If this is your goal, the Weblogic JMS Performance Guide white-paper, available on dev2dev.bea.com, goes into some detail on how to write custom code in 6.1 to more-or-less match the 7.0 distributed destination feature.
Tom

Similar Messages

Error occurred while forwarding a message for distributed destination

Is there a change in the way that Uniform Distributed Destinations are handled in the cluster after weblogic9.2?
I am using oracle weblogic 10.3.0.1 in production mode. I have two managed servers, each managed server has a JMS Server.
I create a Uniform distributed Topic on the System module, and publish a message to it.
I can see the message in the topic on the first JMSServer but the following error happens and the message never makes it to the second JMSServer
<Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on IP:PORT for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "ManSvr1" for domain "Domain" running in Production Mode>
<Sep 24, 2009 2:00:46 PM GMT+00:00> <Notice> <Cluster> <BEA-000102> <Joining cluster Clus on mip:mport>
<Sep 24, 2009 2:00:47 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Sep 24, 2009 2:00:47 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Sep 24, 2009 2:09:52 PM GMT+00:00> <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destination member JMSSystemResource!JMSServer2@example: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with 8935413426058515615S:fqhn:[-1,-1,sslport,sslport,-1,-1,-1]:Domain:ManSvr2, java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:
java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:
java.rmi.ConnectException: Could not establish a connection with 8935413426058515615S:fqhn:[-1,-1,sslport,sslport,-1,-1,-1]:Domain:ManSvr2, java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:

I specified the cluster address, but still get the following errors after a message is published to the topic. Are there other configuration items that can be checked?
<Sep 29, 2009 9:51:49 AM GMT+00:00> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Sep 29, 2009 9:52:01 AM GMT+00:00> <Notice> <Server> <BEA-002613> <Channel "DefaultAdministration" is now listening on 10.241.134.92:7018
for protocols admin, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 29, 2009 9:53:26 AM GMT+00:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 10.241.134.92:7019 for
protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 29, 2009 9:53:26 AM GMT+00:00> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "ClusManSv
r2" for domain "domain" running in Production Mode>
<Sep 29, 2009 9:53:26 AM GMT+00:00> <Notice> <Cluster> <BEA-000102> <Joining cluster Clus on 224.0.0.10:7390>
<Sep 29, 2009 9:53:27 AM GMT+00:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Sep 29, 2009 9:53:27 AM GMT+00:00> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Sep 29, 2009 9:56:14 AM GMT+00:00> <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destinati
on member SOAFJMSSystemResource!SOAFJMSServer1@EventingAdminTopic: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteExc
eption: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,7017,7017,-1,-1,-1]:testnn
2092.net:domain:ClusManSvr1, java.rmi.ConnectException: No known valid port for: 'Def
ault[t3]:t3(t3):managedServer.net:7018:null:-1'; No available router to destination; nested exception is:
java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
ilable router to destination; nested exception is:
java.rmi.ConnectException: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,1
1217,7017,-1,-1,-1]:managedServer.net:domain:ClusManSvr1, java.rmi.ConnectException: No
known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No available router to destination; nested
exception is:
java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
ilable router to destination
weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with 5660061832836428941S:
managedServer.net:[-1,-1,7017,7017,-1,-1,-1]:managedServer.net:domain:
ClusManSvr1, java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; N
o available router to destination; nested exception is:
java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
ilable router to destination; nested exception is:
java.rmi.ConnectException: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,1
1217,7017,-1,-1,-1]:managedServer.net:domain:ClusManSvr1, java.rmi.ConnectException: No
known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No available router to destination; nested
exception is:
java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
ilable router to destination
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchAsync(DispatcherWrapperState.java:158)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchAsync(DispatcherAdapter.java:84)
at weblogic.jms.backend.BEForwardingConsumer$1.run(BEForwardingConsumer.java:503)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.backend.BEForwardingConsumer.processMessages(BEForwardingConsumer.java:499)
Truncated. see log file for complete stacktrace
java.rmi.RemoteException: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,7017,701
7,-1,-1,-1]:managedServer.net:domain:ClusManSvr1, java.rmi.ConnectException: No known v

Using Messaging Bridge with Distributed Destinations

I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
          * WLS Server1:
          * JMS Server1:
          * inbound queue
          * outbound queue
          * JMS Server2:
          * inbound queue
          * outbound queue
          * WLS Server 2:
          * JMS Server3:
          * inbound queue
          * outbound queue
          A distributed destination is configured for the inbound and outbound queues.
          Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
          Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
          Any suggestions?


Hi Rob,
          Consumers on distributed destinations are always pinned
          to a single physical destination on creation. Only
          producers can round-robin each message. When a
          distributed destination is used as a source destination,
          you will need to configure a bridge per distributed
          destination. Alternatively, you can enable
          forwarding between the physical queues, which automatically
          forwards messages from physical queues with
          no consumers to physical queues that have consumers
          (but the extra hop impacts performance). For more information,
          consult the JMS documentation.
          Tom
          Rob McArthur wrote:
          > I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
          > * WLS Server1:
          > * JMS Server1:
          > * inbound queue
          > * outbound queue
          > * JMS Server2:
          > * inbound queue
          > * outbound queue
          > * WLS Server 2:
          > * JMS Server3:
          > * inbound queue
          > * outbound queue
          >
          > A distributed destination is configured for the inbound and outbound queues.
          >
          > Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
          >
          > Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
          >
          > Any suggestions?
          >
          >

[WLST offline]: Cannot create distributed destination

We have a small problem with WLST and distributed destinations. I have made the following code:
readDomain ('< our domain path >/Demo8')
# Check that the queue exists
ls ('/JMSServer/cgJMSServer1/JMSQueue')
create ('myQueue1','JMSDistributedQueue')
cd ('JMSDistributedQueue')
cd ('myQueue1')
set ('JNDIName','myjndi')
create ('member1','JMSDistributedQueueMember')
cd ('JMSDistributedQueueMember')
cd ('member1')
set ('JMSQueue','queue1')
cd ('..')
cd ('..')
UpdateDomain()
The problems is, that the command "set ('JMSQueue','queue1')" fails.
Does anyone have an example of a successful WLST configuration of Distributed Destinations?
The error message from my script is:
Error: setJMSQueue() failed.
Error: set() failed.
Traceback (innermost last):
File "scr.py", line 19, in ?
File "initWls.py", line 46, in set
com.bea.plateng.domain.script.jython.WLSTException: java.lang.reflect.Invocation
TargetException
at com.bea.plateng.domain.script.jython.CommandExceptionHandler.handleEx
ception(CommandExceptionHandler.java:33)
Your help will really be appreciated....
Kind regards,
Henrik

The best way to create distributed destinations is to create physical destinations in single server mode and then create more servers and a cluster. wlst offline will automatically create distribued destinations and members. Considering that the recommended JMS architecture is homogeneous, there is little need to do it manually. An example:
readTemplate('c:/bea813/weblogic81/common/templates/domains/medrec.jar')
cd('JMSServer/MedRecJMSServer')
q=create('newQueue', 'JMSQueue')
q.setJNDIName('newQueue')
cd('/')
create('newServer1', 'Server')
create('newServer2', 'Server')
create('newCluster', 'Cluster')
assign('Server', 'newServer1,newServer2', 'Cluster', 'newCluster')
writeDomain('d:/temp/domains/813/medrec/medrec_0720')
closeTemplate();

Distributed destination issue on Web Logic server 8.1

Hi,
I'm using distributed JMS destination (Cluster) of Web Logic server 8.1.
I'm using Oracle B2B to talk to the cluster. Oracle B2B is only creating a consumer on one of the managed servers in this cluster. This is resulting in loss of messages when messages are placed by the WLI on the other managed server.
Further the consumers are created randomly by Oracle B2B.
My question here is whether Web Logic Server 8.1 supports multiple consumers for its clusters?
Please Help!
Thanks in advance.
Warm Regards,
Suhas.

Are your consumers co-located with each managed server or remote?
Let me preface this by this is the way I believe it works...
The reason I ask is that distributed destinations route to one managed server at connect time. So for producers, when 1 message is placed on a distributed destination, it is really routed to only 1 managed server queue. From a remote consumer standpoint, when connecting to a distributed destination to read messages, you are only routed to one of the managed server queues to read from, not the logical superset of all queues in the distributed destination. So you would need to connect to each distributed destination member queue directly to ensure each had consumers. Whereas if your consumers are co-located on the cluster, then they can each connect to the local member queue for that distributed destination and ensure that each member of the distributed destination has consumers.
I'd recommend you note the follow docs:
QueueReceivers
http://edocs.bea.com/wls/docs103/jms/dds.html
When creating a queue receiver, if the supplied queue is a distributed queue, then a single physical queue member is chosen for the receiver at creation time. The created QueueReceiver is pinned to that queue member until the queue receiver loses its access to the queue member. At that point, the consumer will receive a JMSException, as follows:
If the queue receiver is synchronous, then the exception is returned to the user directly.
If the queue receiver is asynchronous, then the exception is delivered inside of a ConsumerClosedException that is delivered to the ExceptionListener defined for the consumer session, if any.
Upon receiving such an exception, an application can close its queue receiver and recreate it. If any other queue members are available within the distributed queue, then the creation will succeed and the new queue receiver will be pinned to one of those queue members. If no other queue member is available, then the application won’t be able to recreate the queue receiver and will have to try again later.
Note: For information on the load-balancing heuristics for distributed queues with zero consumers, see “Configuring Distributed Destination Resources”.
http://edocs.bea.com/wls/docs103/jms_admin/advance_config.html#jms_distributed_destination_config
The producer makes such a decision each time it sends a message. However, there is no compromise of ordering guarantees between a consumer and producer, because consumers are load balanced once, and are then pinned to a single destination member.

Unable to get distributed destination in cluster

[Cross post with interest.jms]
          Hi,
          I'm working with Weblogic 8.1.2 on Windows. Up until now I've always worked with a single server on which I have configured a JMS server and a number of queues. My clients get references to the queues using the createQueue() method. I now need to test in a clustered environment and my clients are no longer able to create queues; my clients gets a "Invalid destination name" each time.
          I've created a simple cluster with 2 servers and one distributed connection. Each server in the cluster has a uniquely named JMS server. I created a distributed connection called C1_DIST_SECURITY_PERSISTENCE and then created the members automatically for the cluster. My understanding from what I've read is that is the client should no longer need to name the JMS server when calling createQueue, instead the distributed destination name should be sufficient. So, my client calls
          session.createQueue("C1_DIST_SECURITY_PERSISTENCE")
          Everytime it does this it gets the exception: weblogic.jms.common.JMSException: Invalid destination name: C1_DIST_SECURITY_PERSISTENCE
          As an aside I modified my code to try explicitly looking up one of the destination members. In this case a totally different exception occurs:
          eblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Environment not found on thread ] at weblogic.jndi.internal.NamingNodeReplicaHandler.<init>(NamingNodeReplicaHandler.java:150) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
          Any help here greatly appreciated.
          Thanks,
          Aoife

Hi Gsrc,
This is my code in the PR.
public void processRequest(OAPageContext pageContext, OAWebBean webBean)
super.processRequest(pageContext, webBean);
String itemNum=pageContext.getParameter("itemNum");
System.out.println("item nnum "+itemNum);
i am getting a null value in the print stmt.
Thanks.
Message was edited by:
SRK84

JMS distributed destination

In Bea's WLS 7.0 JMS: "Looking up Distributed Topics" and "Deploying Message-Drive
Beans on a Distributed Topic" :
http://e-docs.bea.com/wls/docs70/jms/implement.html#1260828
This sound like each message(topic) gets sent to all members of a distributed
topic.
Then in the same doc for LB, a couple paragraphs down we have a conflict explaination:
"In the round-robin algorithm, WebLogic JMS maintains an ordering of physical
destinations within the distributed destination. The messaging load is distributed
across the physical destinations one at a time in the order that they are defined
in the WebLogic Server configuration (config.xml) file. "
If a topcs sent to a distributed topic will be sent to all physical destinations,
why we need LB here. Or the LB is applied to distributed Queue only.
Please comments.
THX.
-John

Rob,
Not a expert I must admit, but the link provided by you states "A distributed destination is a set of destinations (queues or topics) that are accessible as a single, logical destination to a client. A distributed destination has the following characteristics:
It is referenced by its own JNDI name."
You can actually configure JMS adapters using JNDI so I think this should be possible. More info here,
http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
Do let us know if this helps and works!
Regards
Bhavesh

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

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

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

JMS Failover with Distributed Destinations in 7.0

          How does JMS failover with distributed destinations in WL 7.0?
          In an environment using file stores for persistent messages, can a working server
          automatically pick up unprocessed and persisted messages from a failed server?
          If so, what's the best way to set this up?
          Or, is this completely manual? In other words, we have to bring up a new server
          pointing to the location of the file store from the failed server?


          It appears that two JMSServers cannot share the same file store and, I'm assuming,
          two file stores cannot be using the same directory for persistence.
          So the HA you're talking about is something like Veritas automatically restarting
          a server (or starting a new one) to process the messages in the persistent queue
          that were unprocessed at the time of failure with the file store residing on some
          sort of HA disk array.
          The key point is that a message once it arrives at a server must be processed
          by that server or, in the case of failure of that server, must be processed by
          a server similarly configured to the one that failed so that it picks up the unprocessed
          messages. The message can't be processed by another server in the cluster.
          Or, is there some trick that could be employed to copy from the file store of
          the failed server and repost the messages to the still operating servers?
          "Zach" <[email protected]> wrote:
          >Unless you have some sort of HA framework/hardware, this is a manual
          >operation. You either point to the existing persistent storage (shared
          >storage or JDBC connection pool), or you move the physical data.
          >
          >_sjz.
          >
          >"Jim Cross" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >>
          >> How does JMS failover with distributed destinations in WL 7.0?
          >>
          >> In an environment using file stores for persistent messages, can a
          >working
          >server
          >> automatically pick up unprocessed and persisted messages from a failed
          >server?
          >> If so, what's the best way to set this up?
          >>
          >> Or, is this completely manual? In other words, we have to bring up
          >a new
          >server
          >> pointing to the location of the file store from the failed server?
          >
          >

9.2 migration Distributed Destination Warning message

I migrated the application from 8.1 to 9.2 using migration tool. I'm seeing following warning message in the migration log file. Can I ignore this warning message or Should I take the action for this? Thanks.
The Template named "Queue1" element of Distributed Destination "Queue1" is not supported and hence ignored. Please consider using a Uniform Distributed Destination.

Log an issue against the Runtime project at http://javafx-jira.kenai.com and the javafx devs can take a look at it.

What are distributed destinations?

We seem to have some confusion about what distributed destinations are within WebLogic.
          I believe a distributed topic to be a single topic name (Ex. MyTopic) that will be replicated across multiple weblogic servers. So a publisher publishes a MyTopic message to a "virtual topic" on serverA, it will then be replicated to consumers listening on serverB and serverC as well. So basically this buys you failover, load balancing, and possibly some performance increase.
          Another thought is that a distributed topic can contain multiple topic names within it. For instance, AlphabetTopic is a distributed topic. I can send a message to TopicA which is a entry of AlphabetTopics "child" topics. I can also send a message to TopicB which is part of the AlphabetTopic. It is thought that this will buy us the ability to preserve message ordering across topics because somehow weblogic will be able to maintain ordering across a distributed topic.
          Any information is greatly appreciated.

Let's just say we were only using one host, no cluster.
          1) Can I have a distributed topic (AlphabetTopic), that has 26 topics under it (TopicA-Z) each with a subscriber?
          [Tom] Yes, if there are 26 JMS Servers configured on the single WL server host, where each has one of the DD's physical members. DD's are restricted to working within a single cluster or a single WL server.
          2) What happens if I publish a message directly to TopicA? Does it only go to the physical destinations subscriber?
          [Tom] No. It is still forwarded to all 25 other topics.
          If it were a cluster, would it go to a TopicA physical destination on another node?
          [Tom] Yes. The message would publish directly to TopicA where-ever it resides in the cluster.
          If it is not routed, then in this instance you are not even really using dist topics.
          3) What if I post a message to AlphabetTopic?
          [Tom] If you published to "AlphabetTopic" it would generally first go to a physical topic on the local server (depending on how you've configured your load balancing), and it would also be replicated to all of the other physical topic members.
          My understanding is that it would go to all subscribers listening for TopicA-TopicZ.
          [Tom] Correct.
          Then it would be up to selectors to filter out if all of those clients were to retrieve the message, correct?
          [Tom] Correct.
          Tom

Accessing Distributed destination JNDI Names Web

I am using WebLogic Full Client with Weblogic 10.3. I would like to obtain the JNDI names of the physical members of a Distributed Destination. Weblogic Documentation recommends doing:
"you must look up the JNDI name or the member name using the weblogic.jms.extensions.JMSModuleHelper class uddMakeName and uddMemberJNDIName APIs"
http://download.oracle.com/docs/cd/E11035_01/wls100/jms/dds.html#wp1314556
When I attempt to do the same using the Weblogic full client, I get a class not found exception where a QueueBean class is not found.
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/j2ee/descriptor/wl/QueueBean
at com.overstock.jms.weblogic.ConfigurationMBeanHelper.main(ConfigurationMBeanHelper.java:150)
Caused by: java.lang.ClassNotFoundException: weblogic.j2ee.descriptor.wl.QueueBean
What is the best way to obtain JNDI names of distributed destinations when using Weblogic Full Client? Any code snippets would be valuable.
Thanks.

I think there are a variety of ways to crack this nut. Here are a couple of ideas:
One option would be to write a server side proxy that the client can invoke. For example, a simple EJB (stateless session bean). Another option would be write client-side JMX calls that query either the runtime mbeans or config mbeans to get a list of JMS servers and/or UDD members.
All of these options may require that the domain's administrative server be up and running (not sure). The runtime mbean options would only yield active members.
Tom

JMS Distributed Destinations as proxy service endpoints

We have a cluster of 2 ALSB servers with a proxy service deployed
listening on a JMS queue which is a distributed destination (DD) on a
WLS 8.1 system.
The JMS DD is spread across 4 JMS servers and 4 JVM's.
When ALSB starts up - we only get consumers on 2 of the 4 DD members,
which makes sense as a JMS proxy service is essentially an MDB, and this
is normal MDB/distributed destination behaviour - it will bind to the
queue member where it first makes the connection to the JVM.
How do I make sure my messages are consumed from all 4 DD queue members?
There is a JMS option to forward messages to queues with consumers if no
consumers exist - is that the way to do it?
Someone must have come across this before and I'd be grateful for any
advice.
Also - how do you reduce the consumers on the JMS queue - seems to
default to 16. Perhaps you don't.
Thanks,
Pete

Meghan Pietila wrote:
Update: I see your exchange with Tom over on the JMS forum, Pete. We just switched everything to WLS 9.2, so maybe the ALSB internal extension will work for us. It's not working by default, so possibly it's something that must be activated... I'll follow up with BEA.
http://forums.bea.com/thread.jspa?threadID=570001317
I'd still like to hear what you end up working with, if you don't mind sharing once it's running. :)
MeghanI only have 8.1 as an option - a JMS proxy service is essentially an
MDB, and if you deploy an MDB in the same way, it will only bind to a
single destination, so it's actually behaving as I would expect.
The forward delay on the queue probably won't be an issue for us, as
we're not talking about high volumes and large messages, but for some
sites there will be alot of moving around queues, access jms filestore
etc which you could do without.
I reckon the trick is (as Tom mentioned) to bind to individual
distributed queue members from the proxy service somehow.
I'll let you know what I find out.
Pete

How WLS makes one JMSServer leave or join a distributed destination?

HI,
          According to the WLS documents for Distributed Destination:
          When one member becomes unavalibale due a server failure, traffic is then redirected toward other avaliable destination members in the set.
          Currently, I created two queues and defined two JMS Servers (JMSServer1, JMSServer2). These two JMS Servers are in same distributed destination (JMSDes1).
          My question is
          1) when the JMSServer1 is shutdown, How WLS marked it unavaliable? And How WLS makes it leave the JMSDes1? (If you can know where I can find the documents, it will be greate).
          2) After the JMSServer1 is recycled and is active, how WLS markes it avaliable and makes it join the JMSDes1 again?
          Thanks for any help.

HI,
          According to the WLS documents for Distributed Destination:
          When one member becomes unavalibale due a server failure, traffic is then redirected toward other avaliable destination members in the set.
          Currently, I created two queues and defined two JMS Servers (JMSServer1, JMSServer2). These two JMS Servers are in same distributed destination (JMSDes1).
          My question is
          1) when the JMSServer1 is shutdown, How WLS marked it unavaliable? And How WLS makes it leave the JMSDes1? (If you can know where I can find the documents, it will be greate).
          2) After the JMSServer1 is recycled and is active, how WLS markes it avaliable and makes it join the JMSDes1 again?
          Thanks for any help.

Distributed destination javax.naming.NameNotFoundException

Hi, I have a JMS client (java application) that is trying to publish a message to a JMS queue. This queue is a distributed destination that resides on a cluster with 2 servers.
          When I try to lookup the queue name with
          Queue queue_final = (Queue) ctx.lookup(queueName);
          I get the following exception,
          'LAPPLoanStatusJMSExcep' Resolved [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'LAPPLoanStatusJMSExcep' Resolved ]; remaining name
          I can see this queue name under Distributed destinations and under the 2 servers.

Did you manage to resolve this issue. I appear to be running into the same problem. It only occurs when i am trying to get hold of the queue. I have no problems when i am looking up the connection factory.
          regards
          kodjo

Distributed Destination in WL 6.1SP5

Similar Messages

Maybe you are looking for