Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

how to set plugins (or ihs ) session affinity?

1,204 views
Skip to first unread message

EJour...@gmail.com

unread,
Jul 15, 2008, 5:46:55 AM7/15/08
to
I installed ihs, plugins and was.
and I create a cluster named testCluster. and in the cluster, I
have created two mebers, named s1 ,s2. and the weight set to 2.
when I visite the site. the plugin, send my request to the two
servers alternatly. it means when i have 4 request, It send first and
third to server s1, and sent sencond and the forth to server s2 . but
I want it sent all the request to only one server, like s1.
I don't know where was wrong.
can anyone help me?
thanks a lot

Ben_

unread,
Jul 15, 2008, 6:57:44 AM7/15/08
to
What URL do you invoke ?

Look in the HTTP response if you receive a JSESSIONID cookie and if the
browser sends it back to the server.

EJour...@gmail.com

unread,
Jul 15, 2008, 7:16:26 AM7/15/08
to
On 7月15日, 下午6时57分, "Ben_" <re...@newsgroup.com> wrote:
> What URL do you invoke ?
the URL just like : http://ip/test/test2.jsp

>
> Look in the HTTP response if you receive a JSESSIONID cookie and if the
> browser sends it back to the server.

en, I don't know what does it mean exactly
but i see the cookie of the server in firefox


Ben_

unread,
Jul 15, 2008, 11:55:43 AM7/15/08
to
>> Look in the HTTP response if you receive a JSESSIONID cookie and if the
>> browser sends it back to the server.
>en, I don't know what does it mean exactly
>but i see the cookie of the server in firefox

OK, it's a start.

1- What's the format of the cookie value ? It should be "JSESSIONID =
<random> : <id>". If "<id>" is "-1", the cluster is not correctly setup.

2- Does the value of the cookie change after each request ? It should
normally not.

EJour...@gmail.com

unread,
Jul 15, 2008, 8:40:32 PM7/15/08
to

> 1- What's the format of the cookie value ? It should be "JSESSIONID =
> <random> : <id>". If "<id>" is "-1", the cluster is not correctly setup.
>

Like this: 0001FKx2HQ6TxRhsF2czhBdNa3p:3261TJKMOA


> 2- Does the value of the cookie change after each request ? It should
> normally not.

No, it don't change

but the result is follow
1st request result:
------------------------------------------------------
Server Info22: 10.100.2.93 : 9081

ID FKx2HQ6TxRhsF2czhBdNa3p
Session list
w = w
------------------------------------------------------

2nd request result
----------------------------------------------------
Server Info 10.100.2.94 : 9081

ID FKx2HQ6TxRhsF2czhBdNa3p
Session 列表
w = w
d = d
------------------------------------------------------

So you can see that it has been sent to diffrent servers. not the
first server it reached.
and there some problems, I can't must sent the 2nd request for about 5
seconds later, though to let te sesseion replicated. otherwise, the
"d=d" value should replace "w=w", and don't display the two values.
:-)

rswartwood

unread,
Jul 16, 2008, 9:25:39 AM7/16/08
to

check the plugin log on the IHS server to see if there are any error
messages

marcel....@gmail.com

unread,
Jul 16, 2008, 10:14:35 AM7/16/08
to
Check your plugin for "clone id" this should have a value and takes
care of sessionaffinity within a cluster.
In the plugin.xml you could set log level to trace when you have
enough disk space ;-)

MP.

vilas.w...@gmail.com

unread,
Mar 21, 2014, 4:53:06 AM3/21/14
to
give a wait 0 for s2


gautham...@gmail.com

unread,
Feb 25, 2015, 2:36:18 PM2/25/15
to
Hi

Very simple guys, set a higher weight where you want the request to flow and set the weight with a negative value with the request you want to stop flowing

Thanks
Gautam

freem...@gmail.com

unread,
Apr 11, 2015, 3:26:06 PM4/11/15
to
How did the session get created? Was it via the WASLogin processing or did you programmatically create the session in your application?

Just FYI: If you log into an application server (JVM) and get WAS to return you the session data (HttpRequest.getSession(false) != null) then, by preference, the WAS Plugin will direct subsequent requests back to the same application server. When you programmatically create the session (HttpRequest.getSession(true) or HttpRequest.getSession()) this bypasses the WASLogin processing and the resulting JSESSIONID cookie won't work this way.
0 new messages