RMI load balancing

hi all,
can we do load balancing for BPEL process using RMI calls?
Regards,
terry
Edited by: user11092657 on 29 Apr, 2009 5:38 PM

first thing to remember, an rmi "server" is simply the receiving end of an rmi call (the box which exported a remote object). in a complex distributed system, a box is often both an rmi "client" and an rmi "server". your basic design sounds good. you have one "master" box which is pulling data from the db and distributing the work to one or more "worker" boxes. at the very least, your worker boxes will probably be rmi servers. depending on how you handle job completion (pull vs. push) your master box may also be an rmi server (at the very least, it will be an rmi client).
in terms of overall design, depending on how you pull the data from the database, you could potentially move the database pull to the worker boxes (since pulling data from a db is often a bottleneck as well). if you can define the data to be processed for a single job as a simple query, then you could just send the query info to a worker box and it could pull the data directly from the db and then process it. this could be potentially be much more performant than having one box pull the data and distribute it (for a variety of reasons).

Similar Messages

RMI load Balancing -Any recommendations !

Hi all ,
Any Suggestions to manage and optimize RMI load balancing in a cluster environment ?

first thing to remember, an rmi "server" is simply the receiving end of an rmi call (the box which exported a remote object). in a complex distributed system, a box is often both an rmi "client" and an rmi "server". your basic design sounds good. you have one "master" box which is pulling data from the db and distributing the work to one or more "worker" boxes. at the very least, your worker boxes will probably be rmi servers. depending on how you handle job completion (pull vs. push) your master box may also be an rmi server (at the very least, it will be an rmi client).
in terms of overall design, depending on how you pull the data from the database, you could potentially move the database pull to the worker boxes (since pulling data from a db is often a bottleneck as well). if you can define the data to be processed for a single job as a simple query, then you could just send the query info to a worker box and it could pull the data directly from the db and then process it. this could be potentially be much more performant than having one box pull the data and distribute it (for a variety of reasons).

Rmi load balancer

hey,
i've started writing a basic rmi dispatcher to distribute the work of a search engine and i was wondering what the best way to balance load among available machines on the network would be. does rmi have any built in methods to calculate the workload of a server?
cheers
paul

I know people don't bother to search the forum before posting a question, but this is too much. There is another load-balance thread just above yours. At least you could take the time to look in the current day's threads before posting a new question.

Load balancing on RMI Server Application

Hi there, I'd like to know more detail about load balancing on RMI server application, been digging the web for some time, but couldn't find much information, does anyone know any website or has the knowledge of load balancing on RMI to share? Sort like its design and implementation.
Thanks,
Jax

I want performance and fault-tolerance,
In that case, is it necessary to have a main
rmi server to allow client to access and pick one of
the rmi servers for the client?Well, if you have one main RMI server, you have a single point of failure again.. Why can't your application know about all rmi servers, and randomly choose one? If it's down, pick a different one.. If your applicatoin is an applet, you'll have to sign it.. Do that and put it on 2 redundant web servers. You have performance by splitting the load and you have your fault tolerance by having x identical rmi servers.
If you're saying what I think, why would you have one main rmi server that picks a different rmi server? That's more work AND your redundancy goes byebye, ie if your main rmi server dies..

Load Balancing and Failover in RMI.

Hi All,
I have just one RMI object doing mathematical
calculations.I want failover (and perhaps load
balancing also) for this rmi object.Few Application
servers(like weblogic) provide a wrapper over sun's
rmi to produce replica aware rmi stubs but they force
to use vendor specific (like weblogic rmi-registry)
rmi-registry, which runs within the app server.
My problem is :
I dont want to run the whole app server to just run
one rmi object ?
Is there a way using which I can make replica aware
rmi stubs without using the app server ?
Thanks in advance for the help !!
Regards
Rais

your question is pretty vague. In case you are trying to do load balancing using load balancers then your application layer is actually supposed to be blind as far as the working of the networking layer is concerned (and thats where the load balancers exist). Then the question would also be do you want to achieve this to make the system highly available or make it more resilient and improvr performance. There would be different implementations for both of them. However if you are planning to introduce load balancing programmatically you need to start more than one rmi services.

Load balancing over rmi requests

On a cluster of ias10g (9041), Is it possible that all requests over RMI use a "virtual" hostname and port which directs them to a load balancing mechanism which then determines which of the operational OC4J instances should process this request?

Does anyone know anything on this question?

RMI Clustering/Load Balancing

I want to be able to access a stateless application deployed in an IAS 10g cluster, with a remote client using RMI and have the RMI requests load balanced and failed over between the cluster. The application doesn't use EJBs.
Can anybody tell me how the client RMI requests could be load balanced and failed over accross the cluster?

This is the document you want :- http://download.oracle.com/docs/cd/E12825_01/epm.111/epm_high_avail/launch.html
or pdf version - http://download.oracle.com/docs/cd/E12825_01/epm.111/epm_high_avail.pdf
Cheers
John
http://john-goodwin.blogspot.com/

RMI-P4 Load Balance

Dear all,
We've a landscape as follow:
Primary Application Sever (NetWeaver CE 7.2)
Additional Application Server 1 (NetWeaver CE 7.2), it has 3 nodes
Additional Application Server 2 (NetWeaver CE 7.2), it has 3 nodes
Our client application use ms://<host>:<ms_port>/P4 to get reference to EJB remote interface, it works fine, so we've EJBs from all servers being used to handle our requests.
I would like to define that Primary Application Server must to handle few or no request, just redirect to Additional Application Server, is possible to configure it? Or define a limit to handle requests on Primary Application Server?
How PAS has Database, Web Dynpro Applications and so, I would like to reduce the EJB processing on it and give priority for EJB processing on AAS's, because today I've have a lot of EJB processing on PAS and some nodes of AAS's has not been called.
Best regards

Well as i said i never used the RMI-P4 protocol myself, only http and gui load balancing. It seems logon groups are not mentioned in the documentation for RMI-P4. Usually this is the way to go, to get the msg server to drive request to a certain group of instances.
The message server either keeps a list with response times of the instances and directs requests to the one with the best times. Or for http it distributes more requests to instances with more capacity.
The problem (well it is not necessarly a problem) with your kind of installation, that the response times are usually better on the primary applications server, unless it becomes heavily loaded. That seems to be why most requests go to the primary application server on your system.
Cheers Michael

Load balancing for JSPs and servlets

Hi:
          I am using IIS as the proxy server, with the WLS plug-in, to a WLS
          cluster. This provides round robin load balancing just fine. Will it
          provide weight based load balancing if I set 'weblogic.system.weight'
          differently on each server, or is that not relevant for clustering JSPs
          and servlets?
          Sincerely,
          Ashish


Currently the plugins ( for NES, IIS and Apache) just use the round robin
          algorithm. the property
          weblogic.system.weight is used only be weblogic's replica aware clusterable
          RMI/EJB stubs.
          To use this property for your JSP/Servlet load balancing you have to use
          weblogic server as proxy fron-ending your weblogic cluster.
          --Viresh Garg
          Ashish Vimal wrote:
          > Hi:
          > I am using IIS as the proxy server, with the WLS plug-in, to a WLS
          > cluster. This provides round robin load balancing just fine. Will it
          > provide weight based load balancing if I set 'weblogic.system.weight'
          > differently on each server, or is that not relevant for clustering JSPs
          > and servlets?
          > Sincerely,
          > Ashish

Load balancing with JSP

Anyone and everyone,
When configuring load balancing with Weblogic clusters, does load
balancing take effect for all services or just EJB and RMI? Or another
way of saying the same thing, can I setup weighted load balancing for
the JSP engines across 2 weblogic servers.
Thanks in advance,
Mike

The load-balancing documentation you read describing the different algorithms only applies to RMI stubs (e.g., EJB clients). Please see http://www.weblogic.com/docs51/cluster/concepts.html#1026091 for a description of how load-balancing/clustering works with servlets/JSPs.
The short answer is that in using servlet clustering, most people want/need/use in-memory replication for HttpSession objects. In WLS 5.1 (and before), in-memory replication requires one or more proxy servers be set-up in front of the cluster. Typically, most people use something like BigIP to load-balance
across the proxy servers and let the weblogic plug-in for the proxy server handle the routing to the cluster. The plug-in uses round-robin until an HttpSession is established for a user, then it always tries to route to the server where the user's session is located.
Hope this helps,
Robert
Brian Lin wrote:
All,
I have a quesiton here regarding load balancing with DNS round robin. As of Chapter Adminstration of Clustering Weblogic server, Weblogic can be configured to balance by weight. How about Weblogic handle weight based balancing after DNS round robin ip response? or just can choose one way instead of both?
What's the big difference between choosing BigIP and software balancing (WL)?
Brian
"Wei Guan" <[email protected]> wrote:
I don't think you can configure this load balancing in weblogic in current
release. However, if you have Big-IP or LocalDireoctr, you can set up
weighted load-balancing there. Otherwise, weblogic proxy will use DNS round
robin to do the load-balancing between JSP engins.
My 2 cents.
Cheers - Wei
Michael Yakimisky <[email protected]> wrote in message
news:[email protected]...
Anyone and everyone,
When configuring load balancing with Weblogic clusters, does load
balancing take effect for all services or just EJB and RMI? Or another
way of saying the same thing, can I setup weighted load balancing for
the JSP engines across 2 weblogic servers.
Thanks in advance,
Mike

Load balancing and bean-to-bean method calls

Hello!
          Let's assume the following scenario: a clustered environment, and a
          stateless session bean A accessible by clients. The session bean A then
          makes further calls to other session/entity bean B. Does WebLogic 5.10 do
          load balancing in here? Can we assume that B is always running in the same
          cluster member as A? If not, I assume, that there is quite a bit of
          performance penalty for making the RMI call from B to A?
          Cheers,
          petteri


Petteri Laamanen wrote:
          > Hello!
          >
          > Let's assume the following scenario: a clustered environment, and a
          > stateless session bean A accessible by clients. The session bean A then
          > makes further calls to other session/entity bean B. Does WebLogic 5.10 do
          > load balancing in here? Can we assume that B is always running in the same
          > cluster member as A?
          You mean same server. Yes.
          > If not, I assume, that there is quite a bit of
          > performance penalty for making the RMI call from B to A?
          >
          > Cheers,
          >
          > petteri

WLS6.1sp1 stateful EJB problem = load-balancing and fail over

          I have three problem
          1. I have 2 clustered server. my weblogic-ejb-jar.xml is here
          <?xml version="1.0"?>
          <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
          'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
               <ejb-name>DBStatefulEJB</ejb-name>
               <stateful-session-descriptor>
               <stateful-session-cache>
                    <max-beans-in-cache>100</max-beans-in-cache>
                    <idle-timeout-seconds>120</idle-timeout-seconds>
               </stateful-session-cache>
               <stateful-session-clustering>
                    <home-is-clusterable>true</home-is-clusterable>
                    <home-load-algorithm>RoundRobin</home-load-algorithm>
                    <home-call-router-class-name>common.QARouter</home-call-router-class-name>
                    <replication-type>InMemory</replication-type>
               </stateful-session-clustering>
               </stateful-session-descriptor>
               <jndi-name>com.daou.EJBS.solutions.DBStatefulBean</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          when i use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>"
          and deploy this ejb, exception cause
          <Warning> <Dispatcher> <RuntimeException thrown b
          y rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '2903098842
          594628659S:203.231.15.167:[5001,5001,5002,5002,5001,5002,-1]:mydomain:cluster1',
          oid: '9', implementation: 'weblogic.jndi.internal.RootNamingNode@5f39bc''
          java.lang.IllegalArgumentException: Failed to instantiate weblogic.rmi.cluster.B
          asicReplicaHandler due to java.lang.reflect.InvocationTargetException
          at weblogic.rmi.cluster.ReplicaAwareInfo.instantiate(ReplicaAwareInfo.ja
          va:185)
          at weblogic.rmi.cluster.ReplicaAwareInfo.getReplicaHandler(ReplicaAwareI
          nfo.java:105)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.initialize(ReplicaAwareRem
          oteRef.java:79)
          at weblogic.rmi.cluster.ClusterableRemoteRef.initialize(ClusterableRemot
          eRef.java:28)
          at weblogic.rmi.cluster.ClusterableRemoteObject.initializeRef(Clusterabl
          eRemoteObject.java:255)
          at weblogic.rmi.cluster.ClusterableRemoteObject.onBind(ClusterableRemote
          Object.java:149)
          at weblogic.jndi.internal.BasicNamingNode.rebindHere(BasicNamingNode.jav
          a:392)
          at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.j
          ava:142)
          at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
          2)
          at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
          9)
          at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
          9)
          at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
          9)
          at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
          9)
          at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
          So do i must use it or not???
          2. When i don't use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>"
          , there's no exception
          but load balancing does not happen. According to the document , there's must load
          balancing when i call home.create() method.
          my client program goes here
               DBStateful the_ejb1 = (DBStateful) PortableRemoteObject.narrow(home.create(),
          DBStateful.class);
               DBStateful the_ejb2 = (DBStateful) PortableRemoteObject.narrow(home.create(3),
          DBStateful.class);
          the result is like that
               the_ejb1 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
               daryReplicaHandler@4695a6)/397
               the_ejb2 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
               daryReplicaHandler@acf6e)/398
               or
               the_ejb1 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
               daryReplicaHandler@252fdf)/380
               the_ejb2 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
               daryReplicaHandler@6a0252)/381
               I think the result should be like under one... isn't it??
               the_ejb1 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
               daryReplicaHandler@4695a6)/397
               the_ejb2 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
               daryReplicaHandler@6a0252)/381
          In this case i think the_ejb1 and the_ejb2 must have instance in different cluster
          server
          but they go to one server .
          3. If i don't use      "<home-call-router-class-name>common.QARouter</home-call-router-class-name>",
          "<replication-type>InMemory</replication-type>" then load balancing happen but
          there's no fail-over
          So how can i get load-balancing and fail over together??


          I have three problem
          1. I have 2 clustered server. my weblogic-ejb-jar.xml is here
          <?xml version="1.0"?>
          <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
          'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
               <ejb-name>DBStatefulEJB</ejb-name>
               <stateful-session-descriptor>
               <stateful-session-cache>
                    <max-beans-in-cache>100</max-beans-in-cache>
                    <idle-timeout-seconds>120</idle-timeout-seconds>
               </stateful-session-cache>
               <stateful-session-clustering>
                    <home-is-clusterable>true</home-is-clusterable>
                    <home-load-algorithm>RoundRobin</home-load-algorithm>
                    <home-call-router-class-name>common.QARouter</home-call-router-class-name>
                    <replication-type>InMemory</replication-type>
               </stateful-session-clustering>
               </stateful-session-descriptor>
               <jndi-name>com.daou.EJBS.solutions.DBStatefulBean</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          when i use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>"
          and deploy this ejb, exception cause
          <Warning> <Dispatcher> <RuntimeException thrown b
          y rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '2903098842
          594628659S:203.231.15.167:[5001,5001,5002,5002,5001,5002,-1]:mydomain:cluster1',
          oid: '9', implementation: 'weblogic.jndi.internal.RootNamingNode@5f39bc''
          java.lang.IllegalArgumentException: Failed to instantiate weblogic.rmi.cluster.B
          asicReplicaHandler due to java.lang.reflect.InvocationTargetException
          at weblogic.rmi.cluster.ReplicaAwareInfo.instantiate(ReplicaAwareInfo.ja
          va:185)
          at weblogic.rmi.cluster.ReplicaAwareInfo.getReplicaHandler(ReplicaAwareI
          nfo.java:105)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.initialize(ReplicaAwareRem
          oteRef.java:79)
          at weblogic.rmi.cluster.ClusterableRemoteRef.initialize(ClusterableRemot
          eRef.java:28)
          at weblogic.rmi.cluster.ClusterableRemoteObject.initializeRef(Clusterabl
          eRemoteObject.java:255)
          at weblogic.rmi.cluster.ClusterableRemoteObject.onBind(ClusterableRemote
          Object.java:149)
          at weblogic.jndi.internal.BasicNamingNode.rebindHere(BasicNamingNode.jav
          a:392)
          at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.j
          ava:142)
          at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
          2)
          at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
          9)
          at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
          9)
          at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
          9)
          at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
          9)
          at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
          So do i must use it or not???
          2. When i don't use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>"
          , there's no exception
          but load balancing does not happen. According to the document , there's must load
          balancing when i call home.create() method.
          my client program goes here
               DBStateful the_ejb1 = (DBStateful) PortableRemoteObject.narrow(home.create(),
          DBStateful.class);
               DBStateful the_ejb2 = (DBStateful) PortableRemoteObject.narrow(home.create(3),
          DBStateful.class);
          the result is like that
               the_ejb1 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
               daryReplicaHandler@4695a6)/397
               the_ejb2 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
               daryReplicaHandler@acf6e)/398
               or
               the_ejb1 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
               daryReplicaHandler@252fdf)/380
               the_ejb2 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
               daryReplicaHandler@6a0252)/381
               I think the result should be like under one... isn't it??
               the_ejb1 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
               daryReplicaHandler@4695a6)/397
               the_ejb2 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
               daryReplicaHandler@6a0252)/381
          In this case i think the_ejb1 and the_ejb2 must have instance in different cluster
          server
          but they go to one server .
          3. If i don't use      "<home-call-router-class-name>common.QARouter</home-call-router-class-name>",
          "<replication-type>InMemory</replication-type>" then load balancing happen but
          there's no fail-over
          So how can i get load-balancing and fail over together??

Load-balancing and fail-over between web containers and EJB containers

When web components and EJB components are run in different OC4J instances, can we achieve load-balancing and fail-over between web containers and EJB containers?
null

It looks like there is clustering, but not loadbalancing available for rmi
from the rmi.xml configuration. The application will treat any ejbs on the
cluster as one-to-one look-ups. Orion will go out and get the first ejb
available on the cluster. See the docs on configuring rmi.xml (and also the
note below).
That is a kind-of failover, because if machine A goes down, and the
myotherAejbs.jar are on machine B too, orion will go out and get the bean
from machine B when it can't find machine A. But it doesn't go machine A
then machine B for each remote instance of the bean. You could also specify
the maximum number of instances of a bean, and as one machine gets "loaded",
orion would go to the next available machine...but that's not really
loadbalancing.
That is, you can set up your web-apps with ejbs, but let all of the ejbs be
remote="true" in the orion-application.xml file:
<?xml version="1.0"?>
<!DOCTYPE orion-application PUBLIC "-//Evermind//DTD J2EE Application
runtime 1.2//EN" "http://www.orionserver.com/dtds/orion-application.dtd">
<orion-application deployment-version="1.5.2">
<ejb-module remote="true" path="myotherAejbs.jar" />
<ejb-module remote="true" path="myotherBejbs.jar" />
<ejb-module remote="true" path="myotherCejbs.jar" />
&ltweb-module id="mysite" path="mysite.war" />
... other stuff ...
</orion-application>In the rmi.xml you would define your clustering:
<cluster host="230.0.0.1" id="123" password="123abc" port="9127"
username="cluster-user" />
Tag that is defined if the application is to be clustered. Used to set up
a local multicast cluster. A username and password used for the servers to
intercommunicate also needs to be specified.
host - The multicast host/ip to transmit and receive cluster data on. The
default is 230.0.0.1.
id - The id (number) of this cluster node to identify itself with in the
cluster. The default is based on local machine IP.
password - The password configured for cluster access. Needs to match that
of the other nodes in the cluster.
port - The port to transmit and receive cluster data on. The default is
9127.
username - The username configured for cluster access. Needs to match that
of the other nodes in the cluster.

Distributed naming services for load balancing

Can distributed naming services can be used for load balancing?

ata,
Before jumping to anything so bloated and limited as cougaar, take time to consider what you really need. Before grabing at the fanciest Java features like RMI, JINI, and custom SocketFactories; focus on what you are trying to accomplish.
There are plenty of great answers right here, at this forum.
Good hunting,
John

Sticky Load balancing

Does WLS 5.1 supports Sticky Load Balancing?
          Thank you.
          Rob.


http://www.weblogic.com/docs51/classdocs/javadocs/weblogic/rmi/extensions/CallRouter.html
          - Prasad
          Rob wrote:
          > Looking at the online docs from BEA I found something that I think is what I
          > need. it is called Parameter-based routing
          >
          > It seems that WebLogic Clusters supports several algorithms to address this
          > kind of Load balancing. (something like sticky load balancing)
          >
          > The next text is from the online BEA's docs:
          >
          > Parameter-based routing
          >
          > It is also possible to gain finer grain control over load-balancing. Any
          > clustered object can be assigned a CallRouter. This is a plug-in that is
          > called before each invocation with the parameters of the call. The
          > CallRouter is free to examine the parameters and return the name server to
          > which the call should be routed.
          >
          > If this is correct (that this type of load balancing is slightly the same as
          > sticky load balancing) then the questions is now:
          >
          > What is exactly a CallRouter and where can I see an example of this or more
          > documentation.
          >
          > Rob wrote in message <[email protected]>...
          > >Does WLS 5.1 supports Sticky Load Balancing?
          > >
          > >Thank you.
          > >
          > >Rob.
          > >
          > >
          Cheers
          - Prasad

RMI load balancing

Similar Messages

Maybe you are looking for