JMS Topic Load Balancing on Cluster

Folks
How do we load balance JMS Topic on a cluster.
We have a 2 App Server configuration to a single cluster.
If we have Topic A on both OC4J instances 1,2 - and we send a message to 1 - only clients connected to 1 get the message.
What do we need to do to setup JMS clustering so that the messages sent to Topic A can be handled by both OC4J instances.

Hi Ravi,
Check this forum:
/thread/24959 [original link is broken]
Load Balancing for J2EE Web Applications
http://help.sap.com/saphelp_nw04/helpdata/en/ce/4522d557b26942b202e05ff9ee1f3a/frameset.htm
SAP Web Dispatcher - Load balancing EP6.0 SP2
/thread/19304 [original link is broken]
Reward points if this helps
Regards
Pragathi.

Similar Messages

BPEL + AQ + Load Balancing + OAS Cluster

Hi all
Is there a way to provide load balancing when reading AQ messages (JMS queue, not topic) to a OAS Cluster?
Explaining:
A BPEL server reads a flat file and send JMS messages using an AQ adapter. In the other side, there is a Java application running on a OAS cluster expecting the JMS messages, reading the queue on the AQ. As there is just one queue and many consumers (6 applications instances running on the cluster), how can I provide JMS load balancing between these 6 applications?
Sorry if this is not the correct forum to post, if you could recommend another forum I would be glad.
Thank you
Marcelo

Hi,
thanks for your answer. could you please be more specific? We have found something in the JMS specification:
JMS Spec 1.1 / Sun:
6.11.1 Durable TopicSubscriber
Only one session at a time can have a TopicSubscriber for a particular durable subscription. See
Section 4.3.2, Client Identifier, for more information.
So only one instance (JVM) can have the JMS-connection open to the Topic. How do we load balance these messages then into the Oracle Application Server?
As a workaround, we we have currently deployed a "singleton EAR" which acts as a messaging bridge. It transfers messages from the topic into an "incoming queue" at AQ database. That queue is configured and visible on all OC4j instances. Is this the right way to load balance messages on a OC4J/OAS cluster?
grüße,
\thomas
Edited by: thavemei on 09.11.2009 02:26

JMS Clustering : Load Balancing expected Behaviour

Hi All,
          I have a Cluster with a 2 managed servers A and B . ConnectionFactory is deployed to the cluster and Server B hosts JMS Server.Destinations on the JMS Server are not distributed, but the JNDI Names of the same are replicated across the cluster.Both Load Balancing and server affinity are enabled on the connectionFactory(I hope these attributes are required only if the destinations are distributed).
          An application containing MDBs and EJBs are deployed to the cluster and onMessage MDB looks up for a Facade and makes calls on it.An external java client sets up the initialContext based on the cluster address and starts sending messages to the destination
          What should be the expected behaviour in this scenario ?According to my understanding,
          -Eventhough, the connectionFactory is deployed across the cluster, since the physical destinations are available only in the weblogic server hosting the JMS Server(Server B), the actual message handling(MDB invocation) would be done only here.
          -When the MDBs are invoked on serverB, it would performs a lookup for the Facade.Because of the colocation optimisation, the replica aware stub used would be the one in ServerB and henceforth all the method processing should be done on Server B.
          Is this correct ? But this would also mean that no load balancing would happen because of the colocation optimisation ? Do i need to use a distributed destination to enable load balancing in this scenario ?
          Any help would be greatly appreciated..
          thanks,
          Josh

Hi All,
          I have a Cluster with a 2 managed servers A and B . ConnectionFactory is deployed to the cluster and Server B hosts JMS Server.Destinations on the JMS Server are not distributed, but the JNDI Names of the same are replicated across the cluster.Both Load Balancing and server affinity are enabled on the connectionFactory(I hope these attributes are required only if the destinations are distributed).
          An application containing MDBs and EJBs are deployed to the cluster and onMessage MDB looks up for a Facade and makes calls on it.An external java client sets up the initialContext based on the cluster address and starts sending messages to the destination
          What should be the expected behaviour in this scenario ?According to my understanding,
          -Eventhough, the connectionFactory is deployed across the cluster, since the physical destinations are available only in the weblogic server hosting the JMS Server(Server B), the actual message handling(MDB invocation) would be done only here.
          -When the MDBs are invoked on serverB, it would performs a lookup for the Facade.Because of the colocation optimisation, the replica aware stub used would be the one in ServerB and henceforth all the method processing should be done on Server B.
          Is this correct ? But this would also mean that no load balancing would happen because of the colocation optimisation ? Do i need to use a distributed destination to enable load balancing in this scenario ?
          Any help would be greatly appreciated..
          thanks,
          Josh

OSB jms clustering - load balancing seems to be not working

Hi All,
I have one admin server and two managed servers running ( one of these managed server is running in the remote linux machine) in a cluster
I have connectionfactory created with load balance enabled with round robin
and server affinity is disabled
I have queue created as uniformly distributed Q
I have a proxy service with load balancing as roundrobin and endpoint URL as below
jms://rdoelapp001011:61703,rdoelapp001013:61703/synergyConnectionFactory1/MM_gridQ0
If I execute this proxy sending messages it always go to one server only. There is no message going to the other server.
If I shutdown the server that receives messages then the other server is receiving messages. Seems like fail-over is working but not the load-balancing
There is one point may be worth mentioning here is, from the admin console if I look at the servers for the clusters it has below information
Name State Drop-out Frequency Remote Groups Discovered Local Group Leader Total Groups Discovered Group Leaders Groups Primary
synergyOSBServer1 RUNNING Never 0 synergyOSBServer1 1 synergyOSBServer1 *{synergyOSBServer1}* 0
synergyOSBServer2 RUNNING Never 0 synergyOSBServer1 1 synergyOSBServer1 *{synergyOSBServer1, synergyOSBServer2}* 0
one server has groups as {synergYOSBServer1} instead of {synergyOSBServer1, synergyOSBServer2}. Does that look correct?
here is my jms xml file
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
*<connection-factory name="synergyConnectionFactory1">*
*<sub-deployment-name>synergySubDeploy1</sub-deployment-name>*
*<default-targeting-enabled>false</default-targeting-enabled>*
*<jndi-name>synergyConnectionFactory1</jndi-name>*
*<client-params>*
*<client-id-policy>Restricted</client-id-policy>*
*<subscription-sharing-policy>Exclusive</subscription-sharing-policy>*
*<messages-maximum>10</messages-maximum>*
*</client-params>*
*<transaction-params>*
*<xa-connection-factory-enabled>false</xa-connection-factory-enabled>*
*</transaction-params>*
*<load-balancing-params>*
*<load-balancing-enabled>true</load-balancing-enabled>*
*<server-affinity-enabled>false</server-affinity-enabled>*
*</load-balancing-params>*
*<security-params>*
*<attach-jmsx-user-id>false</attach-jmsx-user-id>*
*</security-params>*
*</connection-factory>*
<uniform-distributed-queue name="errorQ">
<sub-deployment-name>synergySubDeploy1</sub-deployment-name>
<default-targeting-enabled>false</default-targeting-enabled>
<jndi-name>errorQ</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>-1</forward-delay>
<reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>
</uniform-distributed-queue>
<uniform-distributed-queue name="undlvQ">
<sub-deployment-name>synergySubDeploy1</sub-deployment-name>
<default-targeting-enabled>false</default-targeting-enabled>
<jndi-name>undlvQ</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>-1</forward-delay>
<reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>
</uniform-distributed-queue>
*<uniform-distributed-queue name="MM_gridQ0">*
*<sub-deployment-name>synergySubDeploy1</sub-deployment-name>*
*<default-targeting-enabled>false</default-targeting-enabled>*
*<jndi-name>MM_gridQ0</jndi-name>*
*<load-balancing-policy>Round-Robin</load-balancing-policy>*
*<forward-delay>5</forward-delay>*
*<reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>*
*</uniform-distributed-queue>*
<saf-imported-destinations name="synergySAFImportedDest1">
<sub-deployment-name>synergySubDeploy1</sub-deployment-name>
<default-targeting-enabled>false</default-targeting-enabled>
<saf-queue name="gridQ0">
<remote-jndi-name>MB_gridQ0</remote-jndi-name>
<local-jndi-name>gridQ0</local-jndi-name>
<non-persistent-qos>At-Least-Once</non-persistent-qos>
<time-to-live-default>0</time-to-live-default>
<use-saf-time-to-live-default>false</use-saf-time-to-live-default>
<unit-of-order-routing>Hash</unit-of-order-routing>
</saf-queue>
<jndi-prefix>MB_</jndi-prefix>
<saf-remote-context>synergySAFContext1</saf-remote-context>
<saf-error-handling>synergySAFErrorHndlr1</saf-error-handling>
<time-to-live-default>0</time-to-live-default>
<use-saf-time-to-live-default>false</use-saf-time-to-live-default>
<unit-of-order-routing>Hash</unit-of-order-routing>
</saf-imported-destinations>
<saf-remote-context name="synergySAFContext1">
<saf-login-context>
<loginURL>t3://rdoelapp001013:7001</loginURL>
<username>weblogic</username>
<password-encrypted>{AES}z9VY/K4M7ItAr2Vedvhx+j9htR/HkbY2LRh1ED+Cz5Y=</password-encrypted>
</saf-login-context>
<compression-threshold>2147483647</compression-threshold>
</saf-remote-context>
<saf-error-handling name="synergySAFErrorHndlr1">
<policy>Log</policy>
<log-format xsi:nil="true"></log-format>
<saf-error-destination xsi:nil="true"></saf-error-destination>
</saf-error-handling>
</weblogic-jms>
Any help will be greatly appriciated
Edited by: 818591 on Feb 16, 2011 11:28 AM

I am not getting you here "the right approach is to make OSB run on the man server cluster and not on admin server. "
I have a jms proxy service that I created from admin console
And also I have gone thru the step 5 in the link below
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/deploy/config.html#wp1524235
If I am not wrong, the proxy service endpoint URI determines where it is pointing to. If it is a cluster environment, it should point to a clustered address
My proxy has below endpoint URI
jms://rdoelapp001011:61703,rdoelapp001013:61703/synergyConnectionFactory1/MM_gridQ0
and rdoelapp001011:61703,rdoelapp001013:61703 is my cluster address
As per your suggestion "To fix your problem, *make osb to run on the cluster* and specify the same URL for the jms proxy service"
Could you please provide some instruction how would I "make osb jms proxy service to run in a cluster"
As a note, I have Q defined as a distributed Q and connection factory targets to the cluster. UDQ also targtes to the cluster.
Just for a testing I have created another manged server running local to the machine where my admin server is running
And I created a proxy by following steps as I mentioned above and with endpoint URI as below
jms://rdoelapp001011:61703,rdoelapp001013:61703,*rdoelapp001011:61700*/synergyConnectionFactory1/MM_gridQ0
where the new address of my cluster is rdoelapp001011:61703,rdoelapp001013:61703,rdoelapp001011:61700
It did create consumers in both the managed servers in the cluster that are running locally, but no consumers in the remote managed server.
So I am kind of leaning towards thinking that there is some incorrect setup for the remote managed server and may be admin server is not able to communicate to the remote server for some reason but not sure about it..
As a note the cluster is setup to communicate using "unicast" channel
and I created a channel in each manged server with the same name
here is the cluster configuration
<name>synergyCluster1</name>
<cluster-address>rdoelapp001011:61703,rdoelapp001013:61703,rdoelapp001011:61700</cluster-address>
<default-load-algorithm>round-robin</default-load-algorithm>
*<cluster-messaging-mode>unicast</cluster-messaging-mode>*
*<cluster-broadcast-channel>synergyChannel1</cluster-broadcast-channel>*
*<number-of-servers-in-cluster-address>3</number-of-servers-in-cluster-address>*
</cluster>
here are the twoOSBserver configuration
<server>
<name>synergyOSBServer1</name>
<machine xsi:nil="true"></machine>
<listen-port>61703</listen-port>
<cluster>synergyCluster1</cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<server-debug>
<debug-scope>
<name>weblogic.jms.saf</name>
<enabled>true</enabled>
</debug-scope>
<debug-jmssaf>true</debug-jmssaf>
<debug-saf-sending-agent>true</debug-saf-sending-agent>
</server-debug>
<listen-address>localhost</listen-address>
<network-access-point>
*<name>synergyChannel1</name>*
*<protocol>cluster-broadcast</protocol>*
*<listen-address>localhost</listen-address>*
*<listen-port>61702</listen-port>*
<http-enabled-for-this-protocol>true</http-enabled-for-this-protocol>
<tunneling-enabled>false</tunneling-enabled>
*<outbound-enabled>true</outbound-enabled>*
*<enabled>true</enabled>*
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<client-certificate-enforced>false</client-certificate-enforced>
</network-access-point>
<jta-migratable-target>
<user-preferred-server>synergyOSBServer1</user-preferred-server>
<cluster>synergyCluster1</cluster>
</jta-migratable-target>
</server>
<server>
<name>synergyOSBServer2</name>
<ssl>
<enabled>false</enabled>
</ssl>
<machine xsi:nil="true"></machine>
<listen-port>61703</listen-port>
<listen-port-enabled>true</listen-port-enabled>
<cluster>synergyCluster1</cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address>rdoelapp001013</listen-address>
<network-access-point>
*<name>synergyChannel1</name>*
*<protocol>cluster-broadcast</protocol>*
*<listen-address>rdoelapp001013</listen-address>*
*<listen-port>61702</listen-port>*
<http-enabled-for-this-protocol>true</http-enabled-for-this-protocol>
<tunneling-enabled>false</tunneling-enabled>
*<outbound-enabled>true</outbound-enabled>*
*<enabled>true</enabled>*
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<client-certificate-enforced>false</client-certificate-enforced>
</network-access-point>
<java-compiler>javac</java-compiler>
<jta-migratable-target>
<user-preferred-server>synergyOSBServer2</user-preferred-server>
<cluster>synergyCluster1</cluster>
</jta-migratable-target>
<client-cert-proxy-enabled>false</client-cert-proxy-enabled>
</server>
<server>
Edited by: 818591 on Feb 18, 2011 11:26 AM

Load balancing and cluster

Please help on this,
Steps I have created
1. Install Portal on node A
2. Create j2ee cluster instance on node B pointing to node A
3. Software load balance both the nodes
Even after load balancing the two portal nodes,if I shutdown Portal node A dispatcher,then the portal node B dispatcher will automatically shutdown, since the portal node B is a j2ee cluster for Portal node A.In this case how the URL will work from node B ? Please explain

I did portal install on server A. I started dispatcher and I am logging with the URL http://ServerA:52100/irj on server A. And I did install of J2EE cluster on another server called ServerB. I started Server B's dispatcher. When I am starting Server B's dispatcher in Server A I am able to see another time Element joined.The URL for the serverB is http://ServerB:52100/irj. When I created users on Server A, I am able to see the users on Server B.When server B goes down or if dispatcher of B stopped even then Server A is working because it is independent install. But when the Server A goes down which is the main server then the additional J2EE cluster node that is Server B is going down automatically because it is dependent on Server A. But I want to make it as complete high availability of failover,means if Server A goes down it should fail over to Server B and if Server B goes down it should fail over to Server A. I understood we can do software load balancing from windows level or hardware load balancing to get the high availability. But now with my existing installs, I want to make failover to work, please suggest me which is the best way to do without changing any of the existing installs.
My environment is :
Operating system: Windows 2003 Enterprise Edition
Data base: SQL 2000(Already configured as cluster)
Portal: EP6.0 SP2

JMS Failover & Load balancing.

Hi,
I have 4 Managed servers A,B,C,D on 4 physical boxes. We have one JMs server on Box D, All other Managed server uses this only JMS which is on D, if this goes down we loose all messages. I want to have JMS failover in my environment. I suggested to have 4 JMS servers and 4 File stores for each Managed server? my question is that Is weblogic that intellegent that if a client connects to box B JMS server and if the servers goes down, the message will be send top another JMS server?

ravi tiwari wrote:
Hi,
I have 4 Managed servers A,B,C,D on 4 physical boxes. We have one JMs server on Box D, All other Managed server uses this only JMS which is on D, if this goes down we loose all messages. I want to have JMS failover in my environment. I suggested to have 4 JMS servers and 4 File stores for each Managed server? my question is that Is weblogic that intellegent that if a client connects to box B JMS server and if the servers goes down, the message will be send top another JMS server?You don't mention if you're running in a clustered environment or what
version of WLS you're using, so I've assumed a cluster and WLS 8.1
For resiliency, you should really have 4 JMS servers, one on each
managed server. Then each JMS server has it's own filestore on the
physical managed server machine.
So, you have JMSA, JMSB, JMSC, JMSD with FileStoreA, FileStoreB,
FileStoreC & FileStoreD.
You should also look at using JMS distributed destinations as described
in the documentation.
In your current environment, if server D goes down, you not only lose
your messages, your application would lose access to your JMS queues?
If you use distributed destinations, and have 4 JMS servers, your JMS
queues will still be available if a single server goes down.
If a server does go down however, you have to follow the JMS migration
procedures to migrate the JMS service from the failed server to a
running one.
There are conditions to this process, which are best found out from the
migration documentation to be honest, rather than describe it here.
We use this setup, and it works fine for us. We've never had to use JMS
migration, as so far we haven't had anything serious to cause us to need
to migrate. Our servers also boot from a SAN which makes our resilience
processes simpler.
Hope that helps,
Pete

Got request timed out when ping network load balancing (NLB) cluster ip

I want to set up NLB on windows 2008 R2 64
bit
Server1 : private ip 192.168.1.100 ; public ip 172.1.1.1
Server2 : private ip 192.168.1.101 ; public ip 172.1.1.2
private ip 100/101 can be communicated with each other, but cannot reach from other servers, even with same subnet.
Cluster ip: 172.1.1.3
After created NLB with Unicast, I can ping the cluster ip from these 2 servers, but when I enter the cluster ip in browser, got http 404 not found error; and cannot ping the cluster ip from other servers.
Awen

Hi,
In your figure, the cluster IP is 172.18.5.22. Does there have some mistype in your post? Another possible is you set the incorrect IP address binding with the IIS service.
More information:
Add and Remove IP Address Bindings
http://technet.microsoft.com/en-us/library/bb734869.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Who takes care of load balancing work in weblogic cluster ?

Hi Folks,
How load balancing is handled internally by weblogic cluster ? Does Admin server takes care of cluster load balancing ? According to me Admin has nothing to do with load balancing in cluster . Manage server continue to run even when Admin server is down.
I am not looking for explanation about different load balancing algorithm. I am interested in who executes those algorithms in weblogic cluster and how .
Cheers
B.

Hi,
You need to configure loadbalancer and there are different ways to do this. Please go through the below thread to user Apache Loadbalancer.
problem with Apache Proxy plugin
Regards
Suresh.

Error while configuring logon load balancing

Hi,
I am trring to configure logon load balancing in cluster environment.
I had created the logon group using T-Code SMLG and assigned the message server to logon group.
I am using SAP GUI 720.
In the front end system, i had added the host file entry as well as added u201Csapma<SID> 3600/tcpu201D as my CI instance number is 00.
I had created u201Csapmsg.iniu201D and put the entries as below based on sapnote 38119
Message Server
System ID 1>=<Name or IP address of message server 1>
Ex: <SID>=x.x.x.x
 <SID>=x.x.x.x
Message Server Description
<System ID 1>=<Description of message server 1>
Ex: <SID>=CI
But while selecting u201CGroup/Server Selectionu201D I am getting error u201CError: partner x.x.x.x:sapms<SID> not reached u201C.
On the logon pad I had given the following information:
Description: PRD
System ID: <SID>
Message Server: IP address of CI package
I am not able to find the exact reason of the error and how to proceed to resolve the error.
Regards
Dusmanta

> In the front end system, i had added the host file entry as well as added u201Csapma<SID> 3600/tcpu201D as my CI instance number is 00.
> But while selecting u201CGroup/Server Selectionu201D I am getting error u201CError: partner x.x.x.x:sapms<SID> not reached u201C.
> On the logon pad I had given the following information:
> Description: PRD
> System ID: <SID>
Did you enter sapma<SID> or sapms<SID> to the services file on the Windows machine?
Markus

Network Load balancing for Server 2003 and Server 2012

Our environment currently has 2 web servers running Windows Server 2003 with Network Load Balancing. We are looking to update the servers to Windows Server 2012. Is it possible to add Windows Server 2012 into the Windows Server 2003 Network Load
balancing cluster? This way we could bring up 2 new servers add them into the network load balancing and then take out the 2003 servers without disrupting our production.
Any thoughts or suggestions on how to make this work properly?

Hi,
You can upgrade an existing Network Load Balancing (NLB) cluster to Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012 by taking the entire cluster offline
and upgrading all the hosts, or you can leave the NLB cluster online and perform a rolling upgrade. A rolling upgrade entails taking individual cluster hosts offline one at a time, upgrading each host, and returning the host to the cluster. You continue upgrading
individual cluster hosts until the entire cluster is upgraded. A rolling upgrade allows the cluster to continue running during the upgrade.
The related KB:
Upgrading an Existing Network Load Balancing Cluster
http://technet.microsoft.com/en-us/library/cc731691(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Load Balance / Clustering of Oracle9iAS (for EJBs)

Hi there,
I am testing Oracle9iAS and am wondering how load
balancing can be configured with this server. There is
information available about <A
href="http://otn.oracle.com/products/ias/daily/aug27.html"
target=_blank>load balancing for servlets and JSPs</A>, but
I did not find any information about how to load balance or
cluster EJB servers. Does any of you know?
Thank you! 
Chris

Hi there,
I am testing Oracle9iAS and am wondering how load
balancing can be configured with this server. There is
information available about <A
href="http://otn.oracle.com/products/ias/daily/aug27.html"
target=_blank>load balancing for servlets and JSPs</A>, but
I did not find any information about how to load balance or
cluster EJB servers. Does any of you know?
Thank you! 
Chris

Custom Load Balancing Question.

Can anyone give me any pointers on creating a custom load balancing algorithm / cluster proxy..
          Basically i want to have something similar to HttpClusterServlet but that you can customise the load balancing on... for example in a cluster of 6 managed server ms1,ms2,ms3,ms4,ms5,ms6 i want to be able to say this instance of httpclusterservlet only knows about and round robins betwen ms1 and ms2 and ignores ms3-6.
          Can something like that be easily written? I'm trying implement this to run again ALSB so it's mostly webservice calls being made to the proxy. What i'm aimin for in alsb is having one domain across 3 regions each having their own local load balancer balancing to the ms's in their own region).

David Ingham wrote:
          > Can anyone give me any pointers on creating a custom load balancing algorithm / cluster proxy..
          >
          > Basically i want to have something similar to HttpClusterServlet but that you can customise the load balancing on... for example in a cluster of 6 managed server ms1,ms2,ms3,ms4,ms5,ms6 i want to be able to say this instance of httpclusterservlet only knows about and round robins betwen ms1 and ms2 and ignores ms3-6.
          >
          > Can something like that be easily written? I'm trying implement this to run again ALSB so it's mostly webservice calls being made to the proxy. What i'm aimin for in alsb is having one domain across 3 regions each having their own local load balancer balancing to the ms's in their own region).
          I think my answer to your previous emails may start a
          discussion...perhaps you need 3 clusters. By creating your own cluster
          servlet, you're messing around with WLS clustering algorithms which may
          not be a good idea.
          Pete

Load balancing and clustering in sharepoint

Hi,
Still i am confuse about load balancing with cluster in sharepoint level.please let me know how to install and troubleshoot,how it is work, Advantage, etc..
Thanks,
Inguru

Hi Inguru,
Per my knowledge, SharePoint only supports Load balancing and SQL support clustering.
Here is a similar thread for you to take a look:
http://social.technet.microsoft.com/Forums/en-US/2b20d1d5-de35-486e-9b0e-37222a307615/clustering-and-load-balancing?forum=sharepointgeneralprevious
To configure load balancing for SharePoint, please follow the links below:
http://blogs.technet.com/b/praveenh/archive/2010/12/17/setting-up-load-balancing-on-a-sharepoint-farm-running-on-windows-server-2008.aspx
http://community.bamboosolutions.com/blogs/sharepoint-2013/archive/2014/01/07/network-load-balancing-for-sharepoint-2013-part-three-installing-network-load-balancing-on-wfe1-in-a-three-server-farm.aspx
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Load balance with JMS in cluster

 I would like to develop a MDB listening to a topic, which can be deployed in a
 weblogic cluster, so that whenever a message is published to that topic, one and
 only one of the MDB in a wls server of the cluster will process the message, what
 is the best way to do this?
 thanks
 Zhou


Do you desire a distributed topic that doesn't replicate
 between topic members, but replicates
 to all subscribers on a particular member?
 If so, then a distributed topic is NOT
 what you want to configure. Instead, you can do as you
 suggest: set JNDINameReplicated to false
 and put a same JNDI named topic on each server.
 Tom
 Tom Barnes wrote:
 >
 >
 > x zhou wrote:
 >
 >> Can I do the following to achive what I want:
 >
 >
 > I don't know what you want. But a message sent to a topic
 > member still gets replicated to the other topic members.
 >
 > I'm guessing what you are looking for is a
 > distributed queue, not a distributed topic. I suggest
 > you look at the distributed queue option. A message
 > sent to a distributed queue will only get processed
 > by one MDB.
 >
 >>
 >> 1) create a distributed topic having topic name "topic.distributed"
 >> that has "topic.1"
 >> and "topic.2" as its member on two wls instances in a cluster
 >>
 >> 2) write a MDB that will be deployed seperately to 2 wls instances in
 >> the cluster,
 >> with different weblogic-ejb-jar.xml file: the difference is at the line:
 >>
 >> <destination-jndi-name>topic.1</destination-jndi-name> for server 1;
 >> <destination-jndi-name>topic.2</destination-jndi-name> for server 2;
 >>
 >> 3) create the publisher using the distributed topic (of jndi name
 >> 'distribute.topic'),
 >> according the document, it should send the message to one and only one
 >> of its
 >> member, and therefore the corresponding MDB in the wls instance of the
 >> cluster
 >> which receives the message will be notified
 >>
 >> and this will give me multi-threading in the same wls instance
 >> (because of MDB)
 >> and load-balancing across the whole cluster, right?
 >>
 >> Incidently, it looks like I can make the topic member's jndi name the
 >> same, as
 >> long as I un-check the "Replicate JNDI Name In Cluster" checkbox. Why
 >> is there
 >> such a box in the first place? Isn't the topic not clusterable?
 >>
 >> thanks
 >>
 >>
 >> Tom Barnes <[email protected]> wrote:
 >>
 >>> (1) Currently, there is no way in WL to get multiple consumers to share
 >>> a topic subscription - which is essentially what you are asking for.
 >>> The JMS standard doesn't support this either. This is not to say
 >>> that it wouldn't be a useful feature - I personally think it would be.
 >>>
 >>> (2) Why not use a queue?
 >>>
 >>> Tom
 >>>
 >>> X Zhou wrote:
 >>>
 >>>
 >>>> I would like to develop a MDB listening to a topic, which can be
 >>>> deployed
 >>>
 >>>
 >>> in a
 >>>
 >>>> weblogic cluster, so that whenever a message is published to that
 >>>> topic,
 >>>
 >>>
 >>> one and
 >>>
 >>>> only one of the MDB in a wls server of the cluster will process the
 >>>
 >>>
 >>> message, what
 >>>
 >>>> is the best way to do this?
 >>>>
 >>>> thanks
 >>>>
 >>>> Zhou
 >>>
 >>>
 >>
 >

Load balancing In weblogic 6.1 JMS Cluster

 hi
 i have implemented distributed queues in weblogic as suggested in the JMS performance
 guide.but the problem is that of the 3 queues in cluster the messages always end
 up going to the same queue and the remaining 2 remainin queues are empty. i want
 to perfomr load balancing but i think this ios available only in weblogic 7.0.can
 anyone suggest any alternative workaround ??


I wonder if the JNDINameReplicated setting is taking effect.
 Are there any warning or error messages in your logs?
 Can you see statistics for all three JMS servers on the console?
 Does it work if you use the "./a" syntax?
 illusionz70 wrote:
 > hi,
 > 3 machines are in a cluster.all three machines have their different jms servers
 > and queues under them but target teh same connection factory.therefore all three
 > servers target 3 different machines which are in a cluster. i have weblogic 6.1
 > to which i applied the repective CR(patch) which enables the JNDIREPLICATED parameter.i
 > set this parameter to false.as a result i am able to monitor the 3 queues which
 > have the same jndi names but under different servers.but the problem is when i
 > lookup the queues from client using the machine's ip address(not the cluster ip),
 > the results are haywire.... even though i target say a ip of 30 , the msg goes
 > to ip 20... i dont know why..do you have any idea.
 > NOTE : i dont use the ./a ( where queue is the quename ) syntax in createqueue.
 > i look up the queue using the JNDI name.
 > thanks
 > Tom Barnes <[email protected].bea.com>
 > wrote:
 >
 >>Make sure that your context host and connection
 >>factory (CF) host are actually the same as what
 >>you're expecting.
 >>
 >>How, exactly, are your clients:
 >> (A) looking up their context
 >> (B) looking up their CF
 >>
 >>What are the targets for the CF?
 >>What are the URLs for the servers?
 >>What is the URL the clients are using? How is it
 >>load-balanced among the servers?
 >>Are the servers clustered?
 >>
 >>Tom
 >>
 >>illusionz70 wrote:
 >>
 >>
 >>>hi
 >>> i have implemented distributed queues in weblogic as suggested in
 >>
 >>the JMS performance
 >>
 >>>guide.but the problem is that of the 3 queues in cluster the messages
 >>
 >>always end
 >>
 >>>up going to the same queue and the remaining 2 remainin queues are
 >>
 >>empty. i want
 >>
 >>>to perfomr load balancing but i think this ios available only in weblogic
 >>
 >>7.0.can
 >>
 >>>anyone suggest any alternative workaround ??
 >>
 >

JMS Topic Load Balancing on Cluster

Similar Messages

Maybe you are looking for