How to make IIS plug-in do STICKY load balancing

Question

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

Answer 1

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