Sticky load balancing across 2 ports with cookies

Hi,
I have a server configuration where I have 1 top level Apache server that deals with SSL termination (and handles static content) and proxy passes dynamic content onto 2 Tomcat servers on 2 ports, one for http requests (9001) and one for the requests that were secure, but have now been un-encrypted by Apache (9002). My 2 Tomcat servers are load balanced using a CSS and I need this load balancing to stick to the tomcat servers regardless of port so that the user is stuck to the same Tomcat server for their entire session.
I would like to use arrowpoint cookies to perform this stickyness, but the documentation suggests that arrowpoint cookie load balancing (in fact any cookie based load balancing) requires the port to be specified in the content rule. Is this correct? Is my only option to use the source IP for stickyness? I don't understand why the port should be required if the stickyness is via a cookie. Can I not simply configure my 2 tomcat servers as services with no port and add a single content rule that load balances these services using arrowpoint-cookie advanced balancing?
service tomcat1
ip address x.x.x.x
active
service tomcat2
ip address x.x.x.x
active
owner me
   content sticky
     vip address x.x.x.x
     protocol tcp
     url "/*"
     add service tomcat-1
     add service tomcat-2
     advanced-balance arrowpoint-cookie
     active

Angela-
The issue with port is that cookies are very specifically HTTP only and the CSS has no way of knowing what protocol will hit a VIP prior to trying to address it as HTTP. Your issue is actually a bit clearer than it is initially led to be - you can still use 2 different rules by using the configuration below.
However, you might be headed for a headache if you don't implicitly control the client's actions. By default, browsers don't generally send cookies cross-protocol and definitely not cross-domain. Use something like httpwatch or iewatch to check out the headers your client sends to your site. Make sure when the 200ok arrives with the set-cookie that the client sends that cookie in all preceeding packets that are HTTP and HTTPS both.
service tomcat1
string "tomcat1"
ip address x.x.x.x
active
service tomcat2
string "tomcat2"
ip address x.x.x.x
active
owner me
   content sticky9001
     vip address x.x.x.x
     protocol tcp
     url "/*"
     port 9001
     add service tomcat-1
     add service tomcat-2
     advanced-balance arrowpoint-cookie
     active
   content sticky9002
     vip address x.x.x.x
     protocol tcp
     url "/*"
     port 9002
     add service tomcat-1
     add service tomcat-2
     advanced-balance arrowpoint-cookie
     active
With this configuration, the CSS will use the "string" as the cookie value. So if the client were to recieve set-cookie: ArrowpointCookie=tomcat1, it should use it for either rule, and end up on tomcat1 accessing either VIP.
Regards,
Chris

Similar Messages

How to make IIS plug-in do STICKY load balancing

There are two classes of scalable services: pure and sticky. A pure service
is one where any instance of the application can respond to client requests.
A sticky service is one where a client sends its requests to the same
instance; those requests are not redirected to other instances.
It seems to me that weblogic IIS proxy plug-in does not support the sticky
load balancing.
Could someone give me some information on how to make the proxy sticky?
Is there configuration parameters for this?
Thanks,
-Lei

I set the cluster.
It seems to me that there is some problem with the Set-Cookie mechanism of
the plug-in.
Sometime it set the cookie in my browser, sometime it is not.
Even from the wlproxy.log, I could set something like
Fri Aug 03 17:56:12 2001 Hdrs to
client:[Set-Cookie]=[AribaNode=O2tII92qHlP2tpZjUV0m5ued1s6X028cUPu24QcGj1Q25
AE5VXOd!1782877802312707887!ltang.ariba.com!8001!7002; domain=ariba.com;
path=/]
But the cookie is not set in my browser, what might be wrong here?
Thanks,
-Lei
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
I do believe that this will not work since if clustering is not enabled, a
cookie will not be set on the browser that contains the primary and
secondary server.
You are specifying two different ports in your servers. You need to use
clustering in order to get this functionality with the plugin.Furthermore,
you will achieve fail-over.
Regards,
Eric
"Lei Tang" <[email protected]> wrote in message
news:[email protected]...
Here is what I did for the examples under the bea sample directory.
I put the following in test1/WEB-INF/weblogic.xml
<session-descriptor>
<session-param>
<param-name> CookieDomain </param-name>
<param-value> *.ariba.com </param-value>
</session-param>
<session-param>
<param-name> CookieName </param-name>
<param-value> AribaNode </param-value>
</session-param>
<session-param>
<param-name> CookiePath </param-name>
<param-value> /test1 </param-value>
</session-param>
</session-descriptor>
</weblogic-web-app>
I add the following in iisproxy.ini
# This file contains initialization name/value pairs
# for the IIS/WebLogic plug-in.
WebLogicCluster=ltang.ariba.com:8001,achu.ariba.com:7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
Debug=ALL
WLLogFile=c:\tmp\wlproxy.log
WlForwardPath=/test1
DynamicServerList=OFF
CookieName=AribaNode
I use SesssionServlet.java as an example
When I involk http://proxy/test1/SessionServlet, I always get 1
if I use
http://proxy/test1/SessionServlet:AribaNode=................................
I could see the session becomes sticky.
If I do not want to use URL rewriting, what should I do in order to makethe
session STICKY
for this example.
Thanks,
-Lei
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
If you leave the CookieName untouched on the WebLogic side, then there
should be no reason to make the change in the plug-in.
But yes, you need to make sure the cookie names are the same.
Regards,
Eric
"Mark Vaughn" <[email protected]> wrote in message
news:[email protected]...
Actually, you also need to make sure you set the "CookieName" in theplugin.
That let's the plugin read the cookie set by WebLogic to determine
who
the
primary and secondary servers are for that session. Otherwise, theplugin
has no
way of knowing if you are establishing a new session or returning to
an
existing
one. The cookie will tell it if you have a current session and who
it
should
send you to for continuing that session, or failing that session
over.
>>>>
Eric Gross wrote:
Without having clustering enabled, you will not get Sticky load
balancing.
You need to have clustering so that a cookie is sent back to the
client
that
contains information about where it's session is located.
Otherwise,
you
are just going to get round-robin each time.
You can refer to the following page for more information:
http://e-docs.beasys.com/wls/docs61/cluster/servlet.html
Regards,
Eric
"Lei Tang" <[email protected]> wrote in message
news:[email protected]...
WebLogicCluster=machine1:7001,machine2:7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
Debug=ALL
WLLogFile=c:\tmp\wlproxy.log
WlForwardPath=/test,/test1
DynamicServerList=OFF
I run two standone (Admin server) weblogic servers on machine1
machine2.
Then I deploy application test.war on machine1 first, then onmachine2.
Should I make machine2 as a managed server and machine1 as an
admi
n
server?
Will this make the session sticky?
Thanks,
-Lei
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
It would help us to know how you have iisproxy.ini configured.
Sticky
load
balancing should work fine if you have the plug-in and
WebLogic
Server
setup
correctly.
How have you setup the plug-in?
Thanks,
Eric
"Lei Tang" <[email protected]> wrote in message
news:[email protected]...
There are two classes of scalable services: pure and sticky.
A
pure
service
is one where any instance of the application can respond to
client
requests.
A sticky service is one where a client sends its requests to
the
same
instance; those requests are not redirected to other
instances.
It seems to me that weblogic IIS proxy plug-in does notsupport
the
sticky
load balancing.
Could someone give me some information on how to make the
proxy
sticky?
Is there configuration parameters for this?
Thanks,
-Lei
.-. Mark Vaughn
/V\ 7024 Corona Dr.
// \\ North Richland Hills, TX 76180
/( )\ [email protected]
^^-^^
"Give a man a fish and you feed him for a day;
teach him to use the Net and he won't bother you for weeks."
Ben Woodbridge

Sticky load balancing without clustering?

I don't need any type of session replication. I just want to run two
          instances of Weblogic on one machine, one IP, two different ports.
          If I run a third instance of Weblogic for proxying on the same machine
          on yet another port, can I take advantage of the HttpClusterServlet's
          sticky load balancing capabilities if the two Weblogic instances I want
          to proxy between are not participating in a cluster?
          All we require is to have an IP & port that we can hit that will
          round-robin the HTTP requests between the two Weblogic instances, and
          send all subsequent HTTP requests with the same session to the same
          Weblogic instance it sent it to before. Can this work? Thanks in
          advance,
          mg
          Mike Gorman, Director of Architecture
          YOUcentric, Inc.
          Charlotte, NC
          704-643-1000 x518
          http://www.youcentric.com


Thought I read somewhere that you must have different IP addresses for each
          server
          Mike Gorman wrote:
          > I don't need any type of session replication. I just want to run two
          > instances of Weblogic on one machine, one IP, two different ports.
          >
          > If I run a third instance of Weblogic for proxying on the same machine
          > on yet another port, can I take advantage of the HttpClusterServlet's
          > sticky load balancing capabilities if the two Weblogic instances I want
          > to proxy between are not participating in a cluster?
          >
          > All we require is to have an IP & port that we can hit that will
          > round-robin the HTTP requests between the two Weblogic instances, and
          > send all subsequent HTTP requests with the same session to the same
          > Weblogic instance it sent it to before. Can this work? Thanks in
          > advance,
          >
          > mg
          >
          > --
          > Mike Gorman, Director of Architecture
          > YOUcentric, Inc.
          > Charlotte, NC
          > 704-643-1000 x518
          > http://www.youcentric.com

ACE30 load balancing across two slightly different rservers

Hi,
is there a possibility to get a load balancing across two rservers so:
when client sends http://vip/ and it goes to rserver1 then url is sent without change
when client sends http://vip/ and it goes to rserver2 then url is modified to http://vip/xyz/
Or maybe load balancing can be done across two serverfarms ?
thanks

Ryszard,
I hope you are doing great.
I do not think that´s possible since the ACE just load balance the traffic to the servers and once the load balance decision has been taken it will pass the "ball" to the chosen server.
Think about this, let´s say user A needs to go to Server1 but guess what? based on the load balance decision it was sent to Server2 which unfortunately does not have what the customer was looking for. OK, fine, user A close the connection and tries again but now the Server1 is down then the only available is Server2 then the ACE sends it to Server2 again then user A just decides to leave, you see how bad that can be.
A better approach would be to have either 2 VIPs ( different IP addresses) or 2 with the same IP address but hearing on another port, perhaps, one port per server.
Hope this helps!
Jorge

Can't get sticky load balancing to work

I'm really puzzled why sticky LB is not working for a simple case I'm trying. I have two simple JSP's, both registered (see web.xml and ias-web.xml below). I'm using lite session and set distributable to false. Just in case someone can tell by just looking at my session id if it's supposed to be sticky or not, it looks like following -
GXLiteSessionID-4818869464307751325
My two JSP's are also attached below, and they're pretty simple. A new session is supposed to be created in login page and clicking on the logout page invalidates the session.
What I see is that each request (whether login or logout) is randomly sent to any server. For example, if I go to login once, further request to login or logout (whether through refresh or by clicking on the link) is not necessarily sent to the same server.
Any idea what's missing in my setup? I've tried different types of load balancing (round robin, etc.) so I know that's not it.
Thanks a lot in advance.
Jitu
-----web.xml-------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN' 'http://java.sun.com/j2ee/dtds/web-app_2_2.dtd'>
<web-app>
<display-name>WebDesk</display-name>
<distributable>false</distributable>
<servlet>
<servlet-name>TestLogin.jsp</servlet-name>
<jsp-file>TestLogin.jsp</jsp-file>
</servlet>
<servlet-mapping>
<servlet-name>TestLogin.jsp</servlet-name>
<url-pattern>TestLogin.jsp</url-pattern>
</servlet-mapping>
<servlet>
<servlet-name>TestLogout.jsp</servlet-name>
<jsp-file>TestLogout.jsp</jsp-file>
</servlet>
<servlet-mapping>
<servlet-name>TestLogout.jsp</servlet-name>
<url-pattern>TestLogout.jsp</url-pattern>
</servlet-mapping>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name></realm-name>
<form-login-config>
<form-login-page></form-login-page>
<form-error-page></form-error-page>
</form-login-config>
</login-config>
</web-app>
-----ias-web.xml------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ias-web-app PUBLIC '-//Sun Microsystems, Inc.//DTD iAS Web Application 1.0//EN' 'http://developer.iplanet.com/appserver/dtds/IASWebApp_1_0.dtd'>
<ias-web-app>
<servlet>
<servlet-name>TestLogin.jsp</servlet-name>
<guid>{A6D6B277-288D-1C22-C3CA-0800209A2F7C}</guid>
<servlet-info>
<sticky>true</sticky>
<sticky-lb>true</sticky-lb>
</servlet-info>
</servlet>
<servlet>
<servlet-name>TestLogout.jsp</servlet-name>
<guid>{B88B7D19-28B9-1C22-EE63-0800209A2F7C}</guid>
<servlet-info>
<sticky>true</sticky>
<sticky-lb>true</sticky-lb>
</servlet-info>
</servlet>
<session-info>
<impl>lite</impl>
<timeout-type>last-access</timeout-type>
<timeout>60</timeout>
<secure>false</secure>
<domain></domain>
<path>/</path>
<scope></scope>
</session-info>
</ias-web-app>
-----TestLogin.jsp-------
<%
     java.util.Date date = new java.util.Date();
     HttpSession sess = request.getSession(true);
     System.out.println(date + ":TestLogin.jsp: sessionid = " + sess.getId() + ", new = " + sess.isNew());
%>
<HTML>
<HEAD>
<TITLE>TestLogin</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" topmargin=0 leftmargin=0 marginwidth=0 marginheight=0>
<p>
You are now logged in.<br>
<br>
TestLogin.jsp: sessionid = <%=sess.getId()%>, new = <%=sess.isNew()%><br>
<br>
Click here to logout.
</BODY>
</HTML>
----TestLogout.jsp-------
<%
     java.util.Date date = new java.util.Date();
     HttpSession sess = request.getSession(true);
     System.out.println(date + ":TestLogout.jsp: sessionid = " + sess.getId() + ", new = " + sess.isNew());
%>
<HTML>
<HEAD>
<TITLE>TestLogout</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" topmargin=0 leftmargin=0 marginwidth=0 marginheight=0>
<p>
TestLogout.jsp: sessionid = <%=sess.getId()%>, new = <%=sess.isNew()%><br>
<br>
<%
sess.invalidate();
%>
You are now logged out.<br>
<br>
Click here to login.
</BODY>
</HTML>

Hi,
I think it's best to wait for sometime and check the behaviour of sticky load balancing for sometime, the reason being one or more of the following...
- Although sticky feature ensures that the component is run at a single server, when combined with load balancing and under heavy user loads, the load balancing takes place.
- If we rule out the previous case, then, the load balancing mechanism, especially, per component based or per server based, sends request by round robin technique initally(around 128 times or so) and then calculates the effeciency of the response time and then follows the per server based or per component based.
- Meanwhile please ensure that, you have enabled the Sticky LB option under Application using iASAT and please wait for sometime sending requests(probably 130 times) after which it's good to check the mechanism of the sticky bit technique. If it doesn't behaves as it has to then, please let me know and I can help you further on this.
Regards
RG

Load balancing across DMZs - Revisited

I know this question has been asked before and the answer is to have separate content switches per DMZ in order to maintain the security policy. There is an option to have the content switch in front of the firewall and then use only one content switch to load balance across multiple DMZs. Is this an acceptable design or the recommendation is to have a separate content switch behind the firewall for each DMZ of the firewall?
Can a Cisco 6500 with CSM be configured for multiple layer 2 load balanced VLANs thus achieving a mutiple DMZ load balancing scenario with only one switch/CSM?

How do you connect the router to the firewall ?
Problem is the response from the server to a client on the internet.
Traffic needs to get back to the CSS and if the firewall default gateway is the router, the response will not go to the CSS and the CSS will reset it.
If you configure the default gateway of the firewall to be the CSS, than all traffic from your network to the outside will go through the CSS.
This could be a concern as well.
If you don't need to know the ip address of the client for your reporting, you can enable client nat on the CSS to guarantee that server response is sent to the css without having the firewall default gateway pointing at the CSS.
Gilles.

Load balancing across multiple machines

I am looking for assistance in configuring Tuxedo to perform load balancing across
multiple machines. I have successfully performed load balancing for a service
across different servers hosted on one machine but not to another server that's
hosted on a different machine.
Any assistance in this matter is greatly appreciated.

Hello, Christina.
Load balancing with multiple machines is a little bit different than
in the same machine. One of the important resource in this kind
of application is network bandwidth, so tuxedo tries to keep the
traffic among the machines as low as possible. So, it only
balance the load (call services in other machine) in case all the
services are busy in the machine where they are call.
I mean, if you have workstation clients attached only to one
machine, then tuxedo will call services in this machine untill
all servers are busy.
If you want load balancing, try to put one WSL in each machine,
and the corresponding configuration in your WSC ( with the | to
make tuxedo randomly choose one or the other) or spread your
native clients among all the machines.
And so, be carefull with the routing!
Ramón Gordillo
"Christina" <[email protected]> wrote:
>
I am looking for assistance in configuring Tuxedo to perform load balancing
across
multiple machines. I have successfully performed load balancing for a
service
across different servers hosted on one machine but not to another server
that's
hosted on a different machine.
Any assistance in this matter is greatly appreciated.

Load balancing across multiple paths to Internet

Hello,
I have a 2821 router. Currently, I have two bonded T-1 circuits to the Internet.
I would like to add a DSL circuit to augment the T1s. I would also like to load balance across all of the circuits. Currently, IOS performs inherent load balancing for the T1 circuits. The DSL circuit is from a different provider than the T1s.
The T1s are coming from a local ISP that runs no routing protocols within their infrastructure. (They run static routes and rely on the upstream provider for BGP.) The DSL provider is a national telecom carrier.
What is the best way to perform load balancing for this scenario?

Here is the answer (sort of) for anyone reading this post with the same question:
No matter which way I choose to do it, the trick is to have the local ISP subnet advertised via BGP through both pipes. The national telecom DSL provider will not advertise a /20 subnet down a DSL pipe. (Ahh, why not? =:)
Had the secondary pipe been a T-1,T-3, or other traditional pipe, I could have used a load balancer like a BigIP, or FatPipe device or possibly CEF within the IOS.
Case closed. Thanks to everyone that took a look.
Doug.

Load balancing across 4 web servers in same datacentre - advice please

Hi All
Im looking for some advice please
The apps team have asked me about load balancing across some servers but im not that well up on it for applications
Basically we have 4 apache web servers with about 2000 clients connecting to them, they would like to load balance connections to all these servers, they all need the same DNS name etc.
what load balancing methods would I need for this, I believe they run on Linux
Would I need some sort of device, or can the servers run some software that can do this, how would it work? and how would load balancing be achieved here?
cheers

Carl,
What you have mentioned sounds very straightforward then everything should go well.
The ACE is a load balancer which takes a load balancing decisions based on different matching methods like matching virtual address, url, source address, etc then once the load balance decision has been taken then the ACE will load balance the traffic based on the load balance method which you have configured (if you do not configure anything then it will use the default which is "round robin"), then it will send the traffic to the servers which it has available and finally the client should get the content.
If you want to get some details about the load balancing methods here you have them:
http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA3_1_0/configuration/slb/guide/overview.html#wp1000976
For ACE deployments the most common designs are the following.
Bridge Mode
One Arm Mode
Routed Mode
Here you have a link for Bridge Mode and a sample for that:
http://docwiki.cisco.com/wiki/Basic_Load_Balancing_Using_Bridged_Mode_on_the_Cisco_Application_Control_Engine_Configuration_Example
Here you have a link for One Arm Mode and a sample for that:
http://docwiki.cisco.com/wiki/Basic_Load_Balancing_Using_One_Arm_Mode_with_Source_NAT_on_the_Cisco_Application_Control_Engine_Configuration_Example
Here you have a link for Routed Mode and a sample for that:
http://docwiki.cisco.com/wiki/Basic_Load_Balancing_Using_Routed_Mode_on_the_Cisco_Application_Control_Engine_Configuration_Example
Then as you could see in all those links you may end up having a configuration like this:
interface vlan 40
description "Default gateway of real servers"
ip address 192.168.1.1 255.255.255.0
service-policy input remote-access
no shutdown
ip route 0.0.0.0 0.0.0.0 172.16.1.1
class-map match-all slb-vip
2 match virtual-address 172.16.1.100 any
policy-map multi-match client-vips
class slb-vip
    loadbalance vip inservice
    loadbalance policy slb
policy-map type loadbalance http first-match slb
class class-default
    serverfarm web
serverfarm host web
rserver lnx1
    inservice
rserver lnx2
    inservice
rserver lnx3
    inservice
rserver host lnx1
ip address 192.168.1.11
inservice
rserver host lnx2
ip address 192.168.1.12
inservice
rserver host lnx3
ip address 192.168.1.13
inservice
Please mark it if it answered you question then other users can use it as reference in the future.
Hope this helps!
Jorge

IPlanet sticky load balancing question

We have two iPlanet Application Servers v6.0 sp3 and two iPlanet
Enterprise Web servers v4.1. All machines are on the same domain name.
All machines point to the same LDAP server. The application has been
installed on both App servers. Clustering has been configured in the
App server Admin tool to be based upon system load. For non-sticky load
balancing, all works fine, and session information is carried over
properly. However, for sticky load balancing, hits going into either of
the Web servers do not always go back to the App server that first
started the session.
The online iPlanet documentation says it can be done, but we have found
differently. Has anybody else gotten this to work?
Thank you,
David Shade

Hi David,
With sticky load balancing enabled, when you execute the application first
time it will go to any kjs depending on your load banancing criteria which
you set (Round robin or server responce or whatever), this applies to only
for the first time when you send request, afterwords it will be executed in
that perticular KJS process only till that KJS is alive, whatever may be
your LoadB creteria.
You please kill that kjs and see, you will be able to see the failover.
Feel free to mail me for any further information.
Sanjeev,
Developer Support Team iAS-India.
David Shade wrote:
We have two iPlanet Application Servers v6.0 sp3 and two iPlanet
Enterprise Web servers v4.1. All machines are on the same domain name.
All machines point to the same LDAP server. The application has been
installed on both App servers. Clustering has been configured in the
App server Admin tool to be based upon system load. For non-sticky load
balancing, all works fine, and session information is carried over
properly. However, for sticky load balancing, hits going into either of
the Web servers do not always go back to the App server that first
started the session.
The online iPlanet documentation says it can be done, but we have found
differently. Has anybody else gotten this to work?
Thank you,
David Shade--
I have never learn not to learn...
------------------------------------------------------------------

IPTV load balancing across broadcast servers.

I know that across Archive servers in the same cluster that IPTV control server will load balance , is there is a similar function with Broadcast servers. I know broadcast servers use a different delivery mechanism (Multicast). We have multiple broadcast servers that take in an identical live stream, but the only way to advertise thru a URL is a seperate URL per server. Is there some way to hide the multiple URL's to the client population?

No. There is no way to load balance across multiple broadcast servers for live streams. Since this is going to be multicast, there should not be any additional load on the servers when the number of users are more.

NAS 4.0sp6 - sticky load balancing

Hi,
Can anyone tell me if sticky load balancing is required/necessary in a
multi process (8 x kjs's) single threaded (each kjs has only one thread)
environment on one machine. We seem to be getting concurrent session
problems between kjs's.
Platform: Solaris 2.6, NAS 4.0sp6
Thanks in advance.

In general no, but it depends on how your application is written.
In your case, probably yes, but I am only guessing here.
Session is usually distributed through DSYNC and therefore is
serialisable. However, if certain programmers made their objects
non-seriable then they are forcing the sessions to be stored locally and
sticky will help with sending the requests back to the same engine to
get that session.
In your case, I wonder why you are only using 1 thread per kjs. I assume
your application code is not thread safe and therefore you made the
decision to run multiple kjs with single thread only. Following this, I
believe you might also have programmatically made your sessions
local/non ditributable (because of the thread safe issue), thus if this
is the case you probably will require sticky load balancing.
Tosh wrote:
>
Hi,
Can anyone tell me if sticky load balancing is required/necessary in a
multi process (8 x kjs's) single threaded (each kjs has only one thread)
environment on one machine. We seem to be getting concurrent session
problems between kjs's.
Platform: Solaris 2.6, NAS 4.0sp6
Thanks in advance.--
Han-Dat Luc ([email protected])
Senior Consultant
SUN Professional Services (iPlanet)
o .
o .
O _ ____ _ _
(_) _ \| | __ _ _ __ ___| |_ TM
| | |_) | |/ _` | '_ \ / _ \ __|
| | __/| | (_| | | | | __/ |_
|_|_| |_|\__,_|_| |_|\___|\__|
e-commerce solutions
Sun Microsystems Australia Pty Ltd

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

Load balancing across database connection

Do you provide load balancing across database connections and allow RDBMS load
balancing for read only access?
Thanks in advance.

Hello, Christina.
Load balancing with multiple machines is a little bit different than
in the same machine. One of the important resource in this kind
of application is network bandwidth, so tuxedo tries to keep the
traffic among the machines as low as possible. So, it only
balance the load (call services in other machine) in case all the
services are busy in the machine where they are call.
I mean, if you have workstation clients attached only to one
machine, then tuxedo will call services in this machine untill
all servers are busy.
If you want load balancing, try to put one WSL in each machine,
and the corresponding configuration in your WSC ( with the | to
make tuxedo randomly choose one or the other) or spread your
native clients among all the machines.
And so, be carefull with the routing!
Ramón Gordillo
"Christina" <[email protected]> wrote:
>
I am looking for assistance in configuring Tuxedo to perform load balancing
across
multiple machines. I have successfully performed load balancing for a
service
across different servers hosted on one machine but not to another server
that's
hosted on a different machine.
Any assistance in this matter is greatly appreciated.

Clustering not Load balancing on solaris with apache

apache weblogic plugin does not do round-robin , it's kind of random when
          direct the request to the appserver. anyone has seen this problem?
          weblogic5.1 sp9. solaris 2.7 jre1.3.1 rc2


Actually, the random load-balancing when using Apache is caused by the fact
          that Apache (<2.0) spawns multiple processes, so single Apache instance
          will have several plug-in instances running.
          Mike Reiche <[email protected]> wrote:
          > You are using the weblogic plug-in, aren't you?
          > Only new requests are round-robinned. A second request from the same browser
          > is sent to the same server it hit the first time (sticky load-balancing).
          > Mike
          > "Tony Lu" <[email protected]> wrote:
          >>apache weblogic plugin does not do round-robin , it's kind of random
          >>when
          >>direct the request to the appserver. anyone has seen this problem?
          >>
          >>weblogic5.1 sp9. solaris 2.7 jre1.3.1 rc2
          >>
          >>
          Dimitri

Sticky load balancing across 2 ports with cookies

Similar Messages

Maybe you are looking for