JMS in clustered weblogic

Is there any intention of including support for JMS queues clustering? If so, would it include clustering of messages after a server shutdown?
Thanks

Hi Ignacio,
We do not support the JMS API from Coherence. That is one of the APIs that we currently defer to the application server providers, such as BEA. Unfortunately, BEA WebLogic does not currently support Coherence for its clustered queues, but I believe in WebLogic 8.1 you can manually fail-over BEA WebLogic queues in a cluster.
Peace,
Cameron Purdy
Tangosol, Inc.
Coherence: Easily share live data across a cluster!

Similar Messages

What is the association between JMS Server and JMS Module in weblogic 10?

Hi,
I have a created a ConnectionFactory, Queue, Topic under JMS Modules in Weblogic Server 10 using admin console.
And I have created a JMS Server and Targetted to the current running server (Admin Server).
But when I run the Queue Sender program it is unable to LookUP the jndi which I gave for Queue.
queue = (Queue) initialContext.lookup("jndi_queue");
Exception:
javax.naming.NameNotFoundException: Unable to resolve 'jndi_queue'.
But I configured this jndi name when I create the Queue in JMS Module in Weblogic Server 10.
How JMS Module and JMS server are associated.
My Doubt is if i have several JMS Modules and only one JMS Server created then how does the JMS Server identifies which Queue/Topic belongs to which JMS Module????
Please advice.
Thanks....

Hi,
Once you have JMS servers configured:
Step 1: Target the JMS configuration module to the cluster that will host the destination, or, if not using clustering, target the module to the individual WL server that will host the JMS server.
Step 2: Configure a "subdeployment" for the module and set it to reference the exact JMS server(s) that will host the destination. If you're using a distributed desitnation, you can specify multiple JMS servers, if you're using a regular destination, only specify a single destination.
Step 3: Create a destination resource in the module, and set its subdeployment to the subdeployment you specified in step 1 (the console calls this "advanced targeting"). As a best practice avoid the "default targeting" option for the resource - always choose subdeployment (advanced) targeting.
For more information, reference the "best practices" chapter of the JMS configuration guide:
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/best_practice.htm#CACJCGHG
I also I highly recommend the JMS chapter of the book "Professional Oracle WebLogic".
Hope this helps,
Tom

How a clustered weblogic environment handles orders balanced-wise??

Hi,
In a 2 managed clustered weblogic environment with OSM 7.0.3 and an external load balancer to balance the incoming traffic it is noticed from the managed servers that whichever server is scanning for orders and that is understood by the server's logs:
####<Oct 16, 2012 2:54:33 PM EEST> <Info> <oms> <> <osm_ms01> <Timer-9> <oms-internal> <> <fab6ae59fd53672b:704b5627:13a64686216:-8000-0000000000000010> <1350388473505> <BEA-000000> <cluster.ClusteredHandlerFactory: Querying for high activity orders across the cluster>
is the server that will serve a new order.
Is there a way to achieve a perfect load balance? In a test case of 200 orders all orders where processes by one node and it is the one that scans for new orders.
We configured the external load balancer to split the traffic..But nothing!! Is there an internal mechanism that gathers all orders that are send to multiple servers and executes them in the server that is currently scanning for orders ???
Is there in any manual or Oracle Support Document/note on how is decided in a multiple-clustered environment which server will execute orders???
Thx in advance!

Hi Alexandros,
Here's some general information on load balancing:
1. With OSM order affinity, the managed server instance that receives the order (precisely, creates the OSM order) has sole ownership of the order. Other than specific circumstances, the ownership is not transferred, and thus processing of that order stays with that instance till completion.
2. The OSM web service (createOrder API) has no load balancing mechanism internally if HTTP is used as the transport. So if you only send orders to one managed server, that instance will create and thus own all these orders. In contrast, if you use JMS as the transport, it is load-balanced by the JMS distributed destination (provided you are not sending instead to member queues of the distribution destination).
Now, assuming you are using HTTP, you need to ensure that the Load Balancer is really round-robining on the 2 managed servers among HTTP messages of order submissions. Monitor your TCP pipes to verify.
A problem we've seen, is if you are using SoapUI with pre-emptive authentication disabled, the SOAP request without pre-emptive authentication will be rejected, causing a re-send. Because of LB, all orders ended up in one managed server, as the reject-then-accept SOAP message sequence becomes cyclic with odd-even round-robin. So, enable pre-emptive authentication to avoid that.
Btw, is your cartridge handling high-activity orders? If not, I have a suspicion that your pasted log message may be a red-herring.
Cheers,
Daniel Ho
OSM Product Management

Apex Listener and Clustering - WebLogic Server

Has anybody worked with the apex listener on a clustered WebLogic environment with a load balancer? We are having lots of connection issues, and I am wondering if this could be part of the problem.
Thanks,
Michelle

Someone Kindly try to give me reply for my issue .
Thanks& Regards,
Nitesh pareek.

Load Balancing in Clustered Weblogic 12c

Hi,
Weblogic.........: 12.1.3
OS..................: Oracle Enterprise Linux 6.3
We have configured a Clustered Weblogic (2 virtual servers) successfully. Now we are searching for some good Load Balancing solutions. I've tested a ProxyServlet, but it didin't really solve the question, because this kind of load balancing only balances apps in the same server.
Is it mandatory to use a third-party solution, like an Apache Httpd Server, or Big IP? In fact, i would like to know initially for some viable solutions to provide a load balancing solution to a 2-server Weblogic 12c Solution.
Thanks in advance.

Hi,
It is not manadatory, and it is possible to load balance apps on different servers with the ProxyServlet. It's only that this will be running on a server from where the others need to be accesable.
Also, it depends on what you are using this environment for. The ProxyServlet is a good solution if you want to replicate an Enterprise environment and test the load balancing with a WebLogic cluster. However, if you want to run Production applications in this environment, then consider the above suggestions: either a WebServer or a dedicated external Load Balancer.
Regards

Can you specify third party JMS Provider in Weblogic appserver configuration

          Can you specify third party JMS Provider in Weblogic appserver configuration ???
          Only place i know of is that you can specify third party JMS Provider in MDB configuraion.
          DOES Weblogic has some kind of configuration files where you specify JMS Provider
          info (Like you can do that in JBOSS)


You can also specify a third-party JMS provider using the Messaging Bridge,
          which transfers messages from one queue or topic to another.
          And in general, inside WLS you can use any JMS provider you wish anywhere
          that you can also use WLS JMS. In an upcoming release, there will also be
          some support to make foreign JMS providers a little easier to configure.
          But why would you want to use another JMS provider anyway? ;-)
          greg
          "Neeru Munjal" <[email protected]> wrote in message
          news:[email protected]..
          >
          > Can you specify third party JMS Provider in Weblogic appserver
          configuration ???
          >
          > Only place i know of is that you can specify third party JMS Provider in
          MDB configuraion.
          > DOES Weblogic has some kind of configuration files where you specify JMS
          Provider
          > info (Like you can do that in JBOSS)

JMS users on Weblogic

Hi All,
We have created JMS queue on weblogic server which is file base persistent .
Now my query is if any external code wants to publish a message into the queue they need user name to connect .
Which user they can connect other than weblogic user OR what user I can create so that he doesn’t has Admin rights and can publish to Queue.
Thanks
AK

I'm not familiar it, but apparently there's a feature in the security subsystem that allows propagating security information for "L2 Caches" via JMS, and it is this feature that's generating the Warning -- not JMS itself.
I do not happen to know how this feature works, what kind of JMS configuration it expects, or if the Warning is simply a natural ephemeral part of the boot/initialization process of the security feature that can be ignored.
You might want to try posting to the "WebLogic Server - Security" newsgroup.
Tom

Problem in clustered weblogic 9.1 servers duplicating quartz jobs

We have a web application expected to run quartz job to insert one row in database, but it inserted 2 rows in database. The quartz job is kicked off by a servlet that is loaded when weblogic server is started.
I understand the qaurtz job should be clustered with jdbcjobstore, too.
My question is:
if clustered weblogic server is considered as one running instance and the quartz job is kicked by a java servlet that is preloaded when weblogic server started, how could a job shceduled at a specific time (example, 3am daily) will be run twice? i.e. two clustered welogic server each run the job once. Does that mean our weblogic server clustering is not configured right?
The two clustered weblogic servers are on separate Unix machine and synchronized in time.
Any idea for the problem? Just weblogic cluster side, not quartz side.
thanks

The "jsp:directive.include" tag is only valid in an well-formed XML file that specifies all the relevant namespaces. The "jsp:include" tag is used in a JSP file. I'll bet the beginning of your file shows that you don't have a valid and well-formed XML file.
If you found that "jsp:include" worked, then that confirms you have an ordinary JSP file here. Why are you trying to use the XML form? The result of "jsp:include" in a JSP file will be exactly the same as the analogous tag in an XML file.

Foreign JMS QCF and Weblogic Sever Session Pool

          Hi!
          We have Weblogic 6.1 SP2 installation.
          We are trying to use JMS Server session pool and connection consumer configuration
          with MQSeries QCF registered to weblogic JNDI via startup class.
          Upon server startup weblogic is throwing ClassCast exception for QueueConnection.
          It seems weblogic is expecting QueueConnection implementation by weblogic.
          Any suggestions or alternative way of doing it.
          Thanks
          Jay PArikh


Hi Jay,
          Server session pools do not support foreign providers.
          The preferred way to integrate foreign providers is via MDBs or
          via the Messaging Bridge (bridge available in SP3). For a
          comprehensive write-up on integrating foreign providers with
          WL see the whitepaper "Using Foreign JMS Providers with
          WebLogic Server" on dev2dev.bea.com.
          Tom
          Jay Parikh wrote:
          > Hi!
          >
          > We have Weblogic 6.1 SP2 installation.
          >
          > We are trying to use JMS Server session pool and connection consumer configuration
          > with MQSeries QCF registered to weblogic JNDI via startup class.
          >
          > Upon server startup weblogic is throwing ClassCast exception for QueueConnection.
          > It seems weblogic is expecting QueueConnection implementation by weblogic.
          >
          > Any suggestions or alternative way of doing it.
          >
          > Thanks
          > Jay PArikh

How to configure JMS server in weblogic

Hi,
I want to configure JMS server in weblogic.So please send me needful link.
Regards
Anup

Hi Anup,
1. The first thing you have to do is create a filestore where messages will be stored. Look at the below link for more detailed instructions:
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/stores/CreateFileStores.html
2. Next create a JMS server. Look at the below link for more detailed instructions
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_servers/ConfigureJMSServers.html
3. Now, create a JMS System Module to hold the JMS resources like Queues, Topics, Connection Factory, SAF agents etc..
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/modules/ConfigureJMSModules.html
4. Now, create a resource like connection factory OR queue etc.
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/modules/ConfigureJMSModuleResources.html
For now, lets stick to the basics and create a basic queue using the below documentation unless you exactly know what resource you want to create
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/queues/CreateQueues.html
5. You will also need to create a connection factory to use the resource. See below documentation
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/connection_factories/CreateConnectionFactories.html
Please go through the below JMS architecture diagram as well as documentation that will tell you what JMS on WebLogic is all about in terms of configuration
http://docs.oracle.com/cd/E23943_01/web.1111/e13738/overview.htm#i1084283
Arun

JMS Warning on weblogic startup

The JMS experts may here know better. Looking hard to resolve this issue relaated to JMS. can anyone help here.
Re: JMS Warning on weblogic startup

I'm not familiar it, but apparently there's a feature in the security subsystem that allows propagating security information for "L2 Caches" via JMS, and it is this feature that's generating the Warning -- not JMS itself.
I do not happen to know how this feature works, what kind of JMS configuration it expects, or if the Warning is simply a natural ephemeral part of the boot/initialization process of the security feature that can be ignored.
You might want to try posting to the "WebLogic Server - Security" newsgroup.
Tom

Urgent and intresting:weblogic JMS in CLustering

Hi all,
I deployed one application in two different servers(server1,server2) in a weblogic cluster.my application having one MDB .MDB also deployed on all servers.I am sending messages to server1 only by creating Initialcontext as follows.
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, "t3://10.20.30.18:7001");
return new InitialContext(h);
My question is:
1)is there any possible to consume that message by
server2(t3://11.22.33.20:7001) MDB.eventhough iam not putting message on this server.
2)if it is possible then how can i prevent.
3)does connectionfactory/destination(queue) sharable.
Problem faced:
we deployed application 2 days back,first day only server1 MDB consumed Messages,second day server2 MDB started consuming meaasges. we are calling some code from outside of application,we setup that one in only server1,if server2 consumes means it is throwing exception.
we are breaking heads how server2 consuming Messages.

Hi all,
I deployed one application in two different servers(server1,server2) in a weblogic cluster.my application having one MDB .MDB also deployed on all servers.I am sending messages to server1 only by creating Initialcontext as follows.
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, "t3://10.20.30.18:7001");
return new InitialContext(h);
My question is:
1)is there any possible to consume that message by
server2(t3://11.22.33.20:7001) MDB.eventhough iam not putting message on this server.
2)if it is possible then how can i prevent.
3)does connectionfactory/destination(queue) sharable.
Problem faced:
we deployed application 2 days back,first day only server1 MDB consumed Messages,second day server2 MDB started consuming meaasges. we are calling some code from outside of application,we setup that one in only server1,if server2 consumes means it is throwing exception.
we are breaking heads how server2 consuming Messages.

Fail over JMS in clustering

Hi ,
          I'm newbies to weblogic.
          Currently I need to use JMS to asychronous messaging.
          version I used is weblogic 705.
          The environment is clustering. There is one Admin server, and 2 managed servers by multicasting.
          Let's say, there have managed server#1 and managed server#2.
          I set up JMS servers in each instance of managed Servers by using distributed Queue.
          And used MDB to consume the message from queue and deploy to each server.
          used persistance store in DB by JDBC connection Pools which is deploy multipools to cluster.
          when firing hte message using distributed queue, messages keep in persistance store according to load balancing.
          - Is there any work around to support failover?
          Lets say, there fired 20 messages and according to the load balancing, each queue in server server got 10 records. but their persistance is in DB.
          - After firing messages, I intentionally shut down the 2nd server, and restart again. Then MDB consume message which is already send to him. But There have a problem, when restarting the 2nd server, the message in queue( persistance in DB) which is related by 1st serer is wipe out from DB persistance.
          Why can't identify why this one happen.
          Anybody can help me.
          Best regards,

I'm not sure what is your question? Why are the messages stored in the DB wiped out?
          I don't remember WebLogic 7.0 too much, is there a way to setup for JMS migration? If so, you can then migrate from 1 server to another so the messages can be processed even if the server goes down.

Load balancing MQ 7.0 Foreign JMS Server and Weblogic 10 MDBs?

We have the following configuration and we are trying to troubleshoot what appears to be a load balancing issue.
We have 3 Solaris servers. Each Solaris server has two Weblogic managed servers running on it. There are a total of 6 managed servers in the Weblogic cluster.
MQ Series 7.0 is also installed on each Solaris server. The MQ queue managers are in a MQ cluster. Each queue manager has the same queues defined.
We have a foreign JMS Server configured on Weblogic that has destinations and a connection factory defined. There aren't many configuration options available for the connection factory. The destinations are bound to the queues defined on MQ using the MQ bindings file.
The MQ bindings file was generated using the TRANSPORT(BIND) mechanism. Each bindings file points to the queue manager running on that machine. So the 2 managed servers running on one machine are accepting messages from the queue manager on that machine.
The MDB's listenning for messages on the MQ queues are configured as follows in the weblogic-ejb-jar.xml:
<max-beans-in-free-pool>16</max-beans-in-free-pool>
We also created a custom work manager with min threads constraint=5 and max threads constraint=16. The dispatch-policy of all the MDBs is set to the custom work manager.
The open input count on each MQ queue managers shows up as 32 which is expected.
The default load algorithm on the cluster is round-robin.
When we run a load test (injecting 40 messages per second on one MQ queue), we notice that one managed server ends up being significantly loaded than the other. Each MQ queue manager in the MQ cluster receives approximately the same number of messages in the load test. But it seems like one managed server is preferred over the other in Weblogic.
What can be done to equally balance the load among the two managed servers on each Solaris server?
Thanks for the help.

Load balancing generally applies at determing how many consumer threads has to be created on each of the clustered queue instance. In that sense you have achieved perfect load balancing as your queue instances has the same no of consumer threads.
Once you have set 'x' consumer threads on a queue, it is upto messaging provider to decide which thread to deliver a particular message and you will hardly have any control over this. Since your 32 threads are listening on the same queue, MQ can select any thread for delivering the message and the behaviour could be non deterministic.
One option to change your design is to have a dispacther mdb which picks the messages off the MQ and then routes to a weblogic distributed destination and you can have your core mdb which does all processing listen to this distributed destination. You can enable load balancing when the disaptcher mdb routes the message to the distributed destination. Since dispatcher MDB is nothing more than a router, the unbalanced consumption off the MQ shouldn't seriously affect the server.

2 non-clustered weblogic servers, 1 MQ queue. Messaging bridge fairness

Hey all,
          More of a general question. Has anyone ever had 2 non-clustered
          servers, each with a messaging bridge, pulling from one queue? If so, how is
          the fairness of the machines pulling.
          Assuming same machines / same configurations for the weblogic servers,
          should it be
          approximately fair?
          Just want to verify that if the pulling machine sees more messages after
          pulling it's batch,
          it doesn't keep the channel locked or antyhing, before we pursue this
          option.
          Thanks much,
          Greg


Hi Greg,
          The consumer fairness is up to the JMS provider, which sees the bridge
          as a regular consumer no different from any other client consumer.
          If the queue being pulled from is a WebLogic 6.0 or greater queue then
          fairness will be observed. (I'm not sure about earlier versions.) Of
          course, this "fairness" is proportional to the rates at which the
          consumers consume.
          There is no such guarantee for other providers. And in fact, we (BEA)
          have noticed that some of the other well-known JMS vendors do
          not exhibit fairness.
          Tom, BEA
          Greg Kaestle wrote:
          > Hey all,
          >
          > More of a general question. Has anyone ever had 2 non-clustered
          > servers, each with a messaging bridge, pulling from one queue? If so, how is
          > the fairness of the machines pulling.
          > Assuming same machines / same configurations for the weblogic servers,
          > should it be
          > approximately fair?
          >
          > Just want to verify that if the pulling machine sees more messages after
          > pulling it's batch,
          > it doesn't keep the channel locked or antyhing, before we pursue this
          > option.
          >
          > Thanks much,
          > Greg
          >
          >

JMS in clustered weblogic

Similar Messages

Maybe you are looking for