Clustered JMS

I'm trying to config JMS on a clustered WLS.
          Please, is there any link/doc saying how to do it?
          Any comment on this would be welcome.

This should help:
          http://e-docs.beasys.com/wls/docs61/cluster/index.html
          Michael
          BEA Systems
          Learning WebLogic? Buy the book:
          http://www.learnweblogic.com/
          At Amazon:
          http://www.amazon.com/exec/obidos/ASIN/0130911119/learnweblogic/103-6817548-
          3834229
          "Nacho" <[email protected]> wrote in message
          news:3baf0cd4$[email protected]..
          > I'm trying to config JMS on a clustered WLS.
          > Please, is there any link/doc saying how to do it?
          > Any comment on this would be welcome.

Similar Messages

Clustered JMS: license signature validation error

I have encountered the following error when I tried to send JMS message to a queue. Can anyone help to point out what license has been expired and where is it located? Please help
weblogic.jms.common.InvalidDestinationException: Error creating producer: License exception prevents access to destination ImportFileQueue
weblogic.jms.common.JMSException: Clustered JMS: license signature validation error!

JDK 1.2 is a bad choice. I have not seen directories called "java13".
Where, oh where, was my WLS installed?
$ cat $HOME/bea/beahomelist
Which version of WLS are you using?
Your JDK is most likely parallel to wlserver6.1 (?) in jdk131/jre/bin .
Happy Hunting,
Wayne Scott
dave robern wrote:
> After installing (solaris 8) I tried to start the examples server and first
> it could not find java_home (/opt/bea/java13 - I guess the install created
> teh java13 directory but nothing is installed?). I manually configured
> java_home=/usr/java1.2 and then tried again.
>
> Now after using the system password created during installation I get:
>
> $$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
>
> Unable to start WebLogic Server !! WebLogic: license signature validation
> error!
>
> $$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
>
> explain?
>
> Dave

Clustering JMS

Hello,
          I understand that Weblogic's JMS as of 5.0 was not clusterable,
          but that Weblogic 6.0 does have clusterable JMS. How does
          this new JMS implementation stack up against something
          like SonicMQ?
          Thanks,
          Brian Williams


I will leave the sales and marketing to the sales and marketing people. You
          can download weblogic 6.0 and try it for yourself.
          _sjz.
          "Brian Williams" <[email protected]> wrote in message
          news:3a1bf6c9$[email protected]..
          > Hello,
          >
          > I understand that Weblogic's JMS as of 5.0 was not clusterable,
          > but that Weblogic 6.0 does have clusterable JMS. How does
          > this new JMS implementation stack up against something
          > like SonicMQ?
          >
          > Thanks,
          > Brian Williams
          >
          >
          >

Clustered JMS Servers

          I'm having problems with binding the JNDI tree for the other than the first server
          started in the cluster.
          The error looks like this.
          <2001-aug-22 14:31:41 GMT+02:00> <Error> <Cluster> <Conflict start: You tried
          to bind an object under the name EngineRegTopic in the jndi tree. The object you
          have bound weblogic.jms.common.DestinationImpl from 172.18.61.17 is non clusterable
          and you have tried to bind more than once from two or more servers. Such objects
          can only deployed from one server.>
          How come?
          / Martin


I am afraid JMS is not clusterable in WL6.0. Maybe you could try 6.1.
          "Martin" <[email protected]> ¼¶¼g©ó¶l¥ó
          news:3b83ad87$[email protected]..
          >
          > I'm having problems with binding the JNDI tree for the other than the
          first server
          > started in the cluster.
          > The error looks like this.
          > <2001-aug-22 14:31:41 GMT+02:00> <Error> <Cluster> <Conflict start: You
          tried
          > to bind an object under the name EngineRegTopic in the jndi tree. The
          object you
          > have bound weblogic.jms.common.DestinationImpl from 172.18.61.17 is non
          clusterable
          > and you have tried to bind more than once from two or more servers. Such
          objects
          > can only deployed from one server.>
          > How come?
          > / Martin

WLS 7 SP1 - Browsing clustered JMS

          I have made a web application that browse JMS queues by name. This one works perfectly
          when its a none clustered node. When it comes to clustered nodes, I wonder if
          anyone knows where to access these queues... Ive tried queue name at admin server,
          queue name at nodes, and the generated distributed name for the nodes and through
          the admin server aswell... Where and what to access?
          Any ideas is appreciated, I would love to test them out, and if anyone knows the
          resolution... Don't hessitate to answer :)


Although I am not in 7.0 haven yet, we simply target the queue connection
          factory to the cluster in our 6.1 implementation. It does the magic!
          Not sure if its done differently in 7.0.
          AD
          "Klaus Myrseth" <[email protected]> wrote in message
          news:3e004701$[email protected]..
          >
          > I have made a web application that browse JMS queues by name. This one
          works perfectly
          > when its a none clustered node. When it comes to clustered nodes, I wonder
          if
          > anyone knows where to access these queues... Ive tried queue name at admin
          server,
          > queue name at nodes, and the generated distributed name for the nodes and
          through
          > the admin server aswell... Where and what to access?
          >
          > Any ideas is appreciated, I would love to test them out, and if anyone
          knows the
          > resolution... Don't hessitate to answer :)

Single MDB on a clustered JMS queues(2)

I have 2 JMS servers in a cluster and each server has a JMS queue, which forms the distributed destination. Now I need a MDB to listen on both these queues. Is it possible?
Thanks
-Ankur

Yes - thats the usual purpose of distributed queues, to allow consumers to consume from the distributed queue (wherever its hosted).
Though distributed destinations are JMS provider specific so do check your providers documentation on using distributed queues. In some providers, like ActiveMQ, distributed queues look and act just like regular queues so they just work from inside a JMS client or MDB.
James
http://logicblaze.com/

Clustered Durable MDB on Clustered JMS

Hi all
          we have an exception when trying deploy durable MDB in a cluster (WLS 7.0 SP3)
          the cluster have 2 instances. When we depploy Jar on cluster, the first MDB connect successfully, but on the other instances of cluster failed. It's possible couse use the same CLientID?
          This is the exception :
          <7-lug-05 10.54.23 CEST> <Warning> <EJB> <010061> <The Message-Driven EJB: Subsciber2 is unable to connect to the JMS destination: jms/myTopic. The EJB container will automatically attempt to re-establish the connection with the JMS server. This warning may occur during WebLogic Cluster start-up if the JMS destination is located on another server. When the JMS server connection is re-established, the Message-Driven EJB will again receive JMS messages.
          The Error was:
          weblogic.jms.common.InvalidClientIDException: Client id, null, was rejected by the leader
          how can resolve it, using the same client-id?

Hi all
          we have an exception when trying deploy durable MDB in a cluster (WLS 7.0 SP3)
          the cluster have 2 instances. When we depploy Jar on cluster, the first MDB connect successfully, but on the other instances of cluster failed. It's possible couse use the same CLientID?
          This is the exception :
          <7-lug-05 10.54.23 CEST> <Warning> <EJB> <010061> <The Message-Driven EJB: Subsciber2 is unable to connect to the JMS destination: jms/myTopic. The EJB container will automatically attempt to re-establish the connection with the JMS server. This warning may occur during WebLogic Cluster start-up if the JMS destination is located on another server. When the JMS server connection is re-established, the Message-Driven EJB will again receive JMS messages.
          The Error was:
          weblogic.jms.common.InvalidClientIDException: Client id, null, was rejected by the leader
          how can resolve it, using the same client-id?

Application Clustering & JMS

Hi All,
I am in the process of moving an existing application to WebLogic 11g. This applications used to run on OC4J and we used multiple JVMs for the OC4J container to get some scalability.
For WebLogic, we are considering a similar feature and arrived at the WebLogic Cluster with an HTTP-proxy for distributing the incoming traffic. The application depends on certain hard-coded resources.
We have a very simple cluster, consisting of 2 managed Servers: MS1, MS2.
MS1 is the server that physically holds the JMS Server, an MDB to process messages from this JMS queue.
The application is deployed to the entire cluster (MS1+MS2)
After restarting the cluster, we find that the application is available on MS1, but cannot be access from MS2 since the JNDI replication in the cluster seems to take place AFTER the MS2 server has tried to activate the application deployment. Hence, the application is in a failed state on MS2, having run into an javax.naming.NameNotFoundException (after this, WLS tries to perform the JNDI replication across the cluster and it is only after this that the JNDI entries do show on the MS2 server's JNDI tree).
We have multiple queues with multiple consumers, so we do not want to create a distributed queue, since then we would also need to create multiple instance for each consumer (viz. one for each actual destination) ?
This problem occurs both when using a regular and a migratable target for the JMS server setup ...
Any ideas how to prevent the application deployment/activation BEFORE JNDI replication ?
Thx,
Milco

We're having similar problem with distributed destinations:
- 2 managed servers in cluster - MS1 and MS2
- 2 default migratable targets - MS1 (migratable) and MS2 (migratable)
- 2 JMS Servers - JMSServer1 and JMSServer2, 1 on each migratable target
- System JMS Module targeted to cluster
in it: Connection factories targeted to cluster and topics and queues targeted to subdeployment "JMSServer1,JMSServer2"
EAR application, deployed to cluster, is trying to connect to JMS destinations from postStart(ApplicationLifecycleEvent evt).
Understanding is that by the time postStart is called all JMS resources should've been created, but application is getting error
javax.naming.NameNotFoundException: Unable to resolve 'Queue JNDI Name'. Resolved '';
Could anybody help with this?..

Clustered JMS Topics - internal "broadcast"?

          Hi,
          I have a 2-node cluster in WLS 8.1.
          I vaguely remember this may be an old topic but just wanted to make sure. When
          a message is published to a topic, it appears only one of the nodes gets the message.
          And I believe that's by design. If so, what would be a good mechanism for an internal
          broadcast? That is, something happened on one node and it wants everyone in the
          cluster to know.
          TIA,
          Bill


          As jms service is pinned service. That means jms server is pinned to one weblogic
          instance. the messages you send to that topic can only go to that weblogic instance
          where the jms server pinned.
          From my understanding, a distributed topic and load balance can be used if you
          want the messages go to all the iweblogic nstances.
          bin
          "Eric Ma" <[email protected]> wrote:
          >
          >Are you sure only one node gets the message? According to my understanding
          >(have
          >not tried) all nodes get the same messages, which is the desired behavior
          >in your
          >case but a problem for others.
          >
          >Eric Ma
          >
          >"Bill" <[email protected]> wrote:
          >>
          >>Hi,
          >>
          >>I have a 2-node cluster in WLS 8.1.
          >>
          >>I vaguely remember this may be an old topic but just wanted to make
          >sure.
          >>When
          >>a message is published to a topic, it appears only one of the nodes
          >gets
          >>the message.
          >>And I believe that's by design. If so, what would be a good mechanism
          >>for an internal
          >>broadcast? That is, something happened on one node and it wants everyone
          >>in the
          >>cluster to know.
          >>
          >>TIA,
          >>Bill
          >

Can JMS topics and queues be clustered in a WLS 7.0 Cluster?

We are installing a weblogic 7.0 cluster with 1 admin server and 2 managed
          node servers. Two nodes have been clustered. We are at the point where we
          need to configure JMS. Has any one implemented JMS in WLS 7 clustered
          environment? What are the things to watch out when clustering JMS? Can JMS
          topics and queues be clustered?
          TIA for any helpful hints and comments.
          Regards


"Karim Ali" <[email protected]> wrote:
          >> Has any one implemented JMS in WLS 7 clustered
          >> environment?
          I'm currently working on a project with WLS 7 here at work, involving
          the implementation of BEA's JMS Cluster. So far, I really haven't had
          many hiccups.
          "Karim Ali" <[email protected]> wrote:
          >> What are the things to watch out when clustering JMS?
          At least in WLS 7, the biggest thing that stands out is the lack of
          automatic failover. Also, Message Paging -- make sure you configure
          paging high/low thresholds. Or, if you don't wish for it to occur but
          can't stop the server (very common these days with SLAs), set that
          byte/message high threshold to a very large number (correct me if I'm
          wrong, but I believe BEA recommends 2^63 -1).
          "Karim Ali" <[email protected]> wrote:
          >> Can JMS topics and queues be clustered?
          Well, since Topics and Queues are extensions of the
          javax.jms.Destination interface, the answer is: Yes!
          (SIDE NOTE: most people usually refer to them as a [JMS] "destination"
          -- it avoids a lot of conceptual baggage and plus, less typing!)
          You'll probably want to see this section of BEA's e-docs:
          http://edocs.bea.com/wls/docs70/adminguide/jms.html#config_distributed_destinations
          later,
          Brian J. Mitchell
          BEA Systems Administrator
          TRX
          Atlanta, GA
          email: [email protected]
          office: 404-327-7238
          mobile: 678-283-6530

JMS in clustering

Is it possible to deploy JMS across the cluster. I created a cluster with
          four servers and runing 6.0 SP2.
          I also created test MYJMSServer2 ( test) and deplyoed it from console and
          attached all servers and CLUSTER to it in Target.
          I am getting the error message:
          JMSServer "MYJMSServer2", cannot be deployed on multiple servers.
          Appreciate your help.
          Thanks,
          AR


          I'm confused about this explanation. Dose this mean you have to create 4 different
          JMS servers with 4 different JNDI names in the cluster? If so how would a client
          write to a "clustered" JMS server? By looking up its JNDI name? Then what's
          the point of clustering?
          I'm running into this rpoblem as well and would appreciate any clarification
          "Zhenxin Wang" <[email protected]> wrote:
          >
          >Hi, Andy
          >
          >As I remember, as long the app servers of JMS servers form a cluster,
          >the JMS
          >servers are said to be clustered. So, it goes with app servers. As for
          >JMS server,
          >it can only be mapped to one target server. Otherwise, you will get error
          >msgs
          >when you start your app server.
          >
          >Hope it helps.
          >
          >-- zhenxin
          >
          >"Andy Roger" <[email protected]> wrote:
          >>Hi Wang,
          >>
          >>Thanks for the info.
          >>
          >>How can I varify that all four JMS servers, I have created, are part
          >>of
          >>cluster.
          >>
          >>When I go to each server and check for JMS, each server shows 1 JMS
          >server
          >>attached and total 1 server. In my openion, iut should be 1 JMS server
          >>attached and Toatal servers=4, am I missing something here.
          >>
          >>Thanks again for the help.
          >>
          >>AR
          >>
          >>"Zhenxin Wang" <[email protected]> wrote in message
          >>news:[email protected]...
          >>>
          >>> Hi, Andy
          >>>
          >>> Each JMS server can only live in one app server.
          >>> In your scenario, you probably neet to create 4 JMS servers, and attach
          >>each of
          >>> them to a different app server in the cluster.
          >>>
          >>> You can partition your JMS destinations (topics/queues) and distribute
          >>them among
          >>> the JMS servers non-overlappingly.
          >>>
          >>> The clustering feature of JMS means you can send a message to a
          >>destination while
          >>> giving the name or address of the cluster, as long as the the JMS
          >server
          >>(hence
          >>> the app server) hosting the destination is running. However, there
          >>is no
          >>fail
          >>> over with JMS clustering.
          >>>
          >>> Hope that helps.
          >>>
          >>> --Zhenxin Wang
          >>> Principal Software Architect
          >>> Corona Networks
          >>> [email protected]
          >>>
          >>>
          >>> "Andy Roger" <[email protected]> wrote:
          >>> >Is it possible to deploy JMS across the cluster. I created a cluster
          >>> >with
          >>> >four servers and runing 6.0 SP2.
          >>> >
          >>> >I also created test MYJMSServer2 ( test) and deplyoed it from console
          >>> >and
          >>> >attached all servers and CLUSTER to it in Target.
          >>> >
          >>> >I am getting the error message:
          >>> >
          >>> >JMSServer "MYJMSServer2", cannot be deployed on multiple servers.
          >>> >
          >>> >Appreciate your help.
          >>> >
          >>> >Thanks,
          >>> >
          >>> >AR
          >>> >
          >>> >
          >>>
          >>
          >>
          >

Pros and Cons of using REST over JMS (and other technologies)

Hey all,
I am working on a project where we were using JMS initially to send messages between servers. Our front end servers have a RESTful API and use JEE6, with EJB 3.1 entity beans connected to a mysql database and so forth. The back end servers are more like "agents" so to speak.. we send some work for them to do, they do it. They are deployed in GlassFish 3.1 as well, but initially I was using JMS to listen to messages. I learned that JMS onMessage() is not threaded, so in order to facilitate handling of potentially hundreds of messages at once, I had to implement my own threading framework. Basically I used the Executor class. I could have used MDBs, but they are a lot more heavyweight than I needed, as the code within the onMessage was not using any of the container services.
We ran into other issues, such as deploying our app in a distributed architecture in the cloud like EC2 was painful at best. Currently the cloud services we found don't support multi-cast so the nice "discover" feature for clustering JMS and other applications wasn't going to work. For some odd reason there seems to be little info on building out a scalable JEE application in the cloud. Even the EC2 techs, and RackSpace and two others had nobody that understood how to do it.
So in light of this, plus the data we were sending via JMS was a number of different types that had to all be together in a group to be processed.. I started looking at using REST. Java/Jersey (JAX-RS) is so easy to implement and has thus far had wide industry adoption. The fact that our API is already using it on the front end meant I could re-use some of the representations on the back end servers, while a few had to be modified as our public API was not quite needed in full on the back end. Replacing JMS took about a day or so to put the "onmessage" handler into a REST form on the back end servers. Being able to submit an object (via JAXB) from the front servers to the back servers was much nicer to work with than building up a MapMessage object full of Map objects to contain the variety of data elements we needed to send as a group to our back end servers. Since it goes as XML, I am looking at using gzip as well, which should compress it by about 90% or so, making it use much less bandwidth and thus be faster. I don't know how JMS handles large messages. We were using HornetQ server and client.
So I am curious what anyone thinks.. especially anyone that is knowledgeable with JMS and may understand REST as well. What benefits do we lose out on via JMS. Mind you, we were using a single queue and not broadcasting messages.. we wanted to make sure that one and only one end server got the message and handled it.
Thanks..look forward to anyone's thoughts on this.

851827 wrote:
Thank you for the reply. One of the main reasons to switch to REST was JMS is strongly tied to Java. While I believe it can work with other message brokers that other platforms/languages can also use, we didn't want to spend more time researching all those paths. REST is very simple, works very well and is easy to implement in almost any language and platform. Our architecture is basically a front end rest API consumed by clients, and the back end servers are more like worker threads. We apply a set of rules, validations, and such on the front end, then send the work to be done to the back end. We could do it all in one server tier, but we also want to allow other 3rd parties to implement the "worker" server pieces in their own domains with their own language/platform of choice. Now, with this model, they simply provide a URL to send some REST calls to, and send some REST calls back to our servers.well, this sounds like this would be one of those requirements which might make jms not a good fit. as ejp mentioned, message brokers usually have bindings in multiple languages, so jms does not necessarily restrict you from using other languages/platforms as the worker nodes. using a REST based api certainly makes that more simple, though.
As for load balancing, I am not entirely sure how glassfish or JBoss does it. Last time I did anything with scaling, it involved load balancers in front of servers that were session/cookie aware for stateful needs, and could round robin or based on some load factor on each server send requests to appropriate servers in a cluster. If you're saying that JBoss and/or GlassFish no longer need that.. then how is it done? I read up on HornetQ where a request sent to one ip/hornetq server could "discover" other servers in a cluster and balance the load by sending requests to other hornetq servers. I assume this is how the JEE containers are now doing it? The problem with that to me is.. you have one server that is loaded with all incoming traffic and then has to resend it on to other servers in the cluster. With enough load, it seems that the glassfish or jboss server become a load balancer and not doing what they were designed to do.. be a JEE container. I don't recall now if load balancing is in the spec or not..I would think it would not be required to be part of a container though, including session replication and such? Is that part of the spec now?you are confusing many different types of scaling. different layers of the jee stack scale in different ways. you usually scale/load balance at the web layer by putting a load balancer in front of your servers. at the ejb layer, however, you don't necessarily need that. in jboss, the client-side stub for invoking remote ejbs in a cluster will actually include the addresses for all the boxes and do some sort of work distribution itself. so, no given ejb server would be receiving all the incoming load. for jms, again, there are various points of work to consider. you have the message broker itself which is scaled/load balanced in whatever fashion it supports (don't know many details on actual message broker impls). but, for the mdbs themselves, each jee server is pretty independent. each jee server in the cluster will start a pool of mdbs and setup a connection to the relevant queue. then, the incoming messages will be distributed to the various servers and mdbs accordingly. again, no single box will be more loaded than any other.
load balancing/clustering is not part of the jee "spec", but it is one of the many features that a decent jee server will handle for you. the point of jee was to specify patterns for doing work which, if followed, allow the app server to do all the "hard" parts. some of those features are required (transactions, authentication, etc), and some of those features are not (clustering, load-balancing, other robustness features).
I still would think dedicated load balancers, whether physical hardware or virtual software running in a cloud/VM setup would be a better solution for handling load to different tiers?like i said, that depends on the tier. makes sense in some situations, not others. (for one thing, load-balancers tend to be http based, so they don't work so well for non-http protocols.)

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 deployed to cluster of servers

Hey guys,
I was trying to deploy a JMS server to a cluster of servers and in the target section there wasn't an option for the cluster. They had an option for each individual server and another migratable version of the server. If I target one of the migratable servers in the cluster will it apply to all of the servers?
I read the following passage in the weblogic documents:
Obtain a Clustered JMS Licence
In order to implement JMS clustering, you must have a valid clustered JMS license, which allows a connection factory and a destination to be on different WebLogic Server instances. A clustered JMS license is also required to use the Foreign JMS Providers feature, as described in "Simple Access to Remote or Foreign JMS Providers" in the Administration Console Online Help. If you do not have a valid clustered JMS license, contact your BEA sales representative.
If i'm just building a model does this apply to me?
Thanks

continued reading to clarify. Problem solved, thanks for looking

Distributed JMS Question

Domain 1 (host1)
=========
I have 2 JMS servers target to 2 managed servers. I have Distributed Queues (distqueue1 & distqueue2) in a module targetted to both of the jms servers.
Where Managed server 1 --> Host 1
Managed server 2 --> Host 2
Domain 2 (host2)
========
I have an application deployed on the clustered environment.
=============================================================-
Till now I use to have my app connected to (Domain 1(host1)) to one jms server (targetted on ManagedServer 1), now I want my application to do lookup to the clustered JMS on both the servers.
So my question is how we proceed with the application to talk to the clustered jms (on multiple managed servers (on multiple physical hosts))

You can specify the distributed destination JNDI name for the destination. Weblogic provides cluster wide JNDI replication - so any object that is deployed to any of the managed servers or to the cluster will be visible in the global JNDI tree of all the managed servers in the cluster. So for the JNDI lookup you can connect to a single managed server, or, A better load balanced approach would be to use a dns lookup where your app connects to a dns name and the dns is resolved to different IP address ( man1 IP, man 2 IP etc) on each lookup.
You will have to get the load balancing setup on the Connection factory and the CF has to be deployed to a cluster to avoid unwanted routing between the man servers.
This has been discussed a lot in the jms forum. Please search and you will get more details.
One good link I got with a quick search
Clustering with a load balancer
Edited by: atheek1 on 25-Mar-2010 01:02

Clustered JMS

Similar Messages

Maybe you are looking for