Hallo Ahmed,
Ahmed Musa wrote:
Hi,
i have the following situation
Apache is balancing requests to backend JBoss Server . Everything (the
balancing of requests to the webcontainer (tomcat) of jboss)works fine - except
i cannot get the balancer-manager working.
Of course the GUI appears but after clicking on a worker link nothing happens.
Apache 2.2.3 on Suse Linux Enterprise Version 10
<Proxy balancer://portal>
Order deny,allow
Allow from all
BalancerMember ajp://lx-tpor01.xxxx.xxxxxxx.xx:8009/portal route=jboss11
BalancerMember ajp://lx-tpor01.xxxx.xxxxxxx.xx:18009/portal
route=jboss12
and so on.......
</Proxy>
ProxyPass /portal balancer://portal stickysession=JSESSIONID
lbmethod=byrequests nofailover=Off
ProxyPass /balancer-manager !
<Location /balancer-manager>
SetHandler balancer-manager
Order Deny,Allow
Deny from all
Allow from xxxxxx
</Location>
I got the follwing gui
LoadBalancer Status for balancer://portal
StickySession Timeout FailoverAttempts Method JSESSIONID 0 7 byrequests
Worker URL Route RouteRedir Factor Status
ajp://lx-tpor01.xxxx.xxxxxxx.xx:8009/portal jboss11 1 Ok
ajp://lx-tpor01.xxxx.xxxxxxx.xx:18009/portal jboss12 1 Ok
and so on
but if i disable one Jboss instance the status remains on ok, and if i click on
a worker url i don't get the possibility to edit the attribute - only the url
is changing without any change in the gui.
also when i click on the balancer nothing happens.
i appreciate any help - thanxs in advance
ahmed
I just tried it with httpd 2.2.8 and it works for me. Although there
seeems to be no fit in the httpd changelog, 2.2.3 is a little early in
the 2.2.x release cycle and the balancer and balancer manager were new
in 2.2.x, so if nothing else helps, upgrading to a more recent 2.2.x
(like 2.2.8 or 2.2.9 expected in a few weeks) would be worth trying. I
think I remember having it used with 2.2.6, but I didn't try it with
2.2.3 or earlier.
Others?
Apart from that: the httpd users list might be a better place to ask,
because this seems not to be related to some difficult AJP13 stuff
instead it seems to be a more general httpd mod_proxy_* issue.
Regards und Grüße nach Wien
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: [email protected]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
