________________________________

        From: juergen.l...@it.nrw.de [mailto:juergen.l...@it.nrw.de] 
        Sent: Monday, July 06, 2009 5:29 PM
        To: users@httpd.apache.org
        Subject: [us...@httpd] mod_proxy_balance: route redirect not working
        
        
        We use mod_proxy to distribute requests to four tomcat instances.
        Our configuration (vhost.conf) is as follows:
         
        <VirtualHost aa.bb.cc:3000>
           ProxyPass /balancer-manager !
           ProxyPass / balancer://mybalancer/ stickysession=JSESSIONID
         
           <Proxy balancer://mybalancer>
                BalancerMember ajp://xx.yy.zz:11009/ldsportal route=tomcat1 
loadfactor=50
                BalancerMember ajp://xx.yy.zz:12009/ldsportal route=tomcat2 
loadfactor=50
                BalancerMember ajp://xx.yy.zz:13009/ldsportal route=tomcat3 
loadfactor=50
                BalancerMember ajp://xx.yy.zz:13009/ldsportal route=tomcat4 
loadfactor=50
           </Proxy>
         
           <Location /balancer-manager>
                SetHandler balancer-manager
           </Location>
        </VirtualHost>
        
        Things work fine this way, but occasionally, we have to shut down a 
single instance for maintenance.
        We use the balancer manager to reconfigure the respective worker (say: 
tomcat1) to redirect to another worker:
        - select the instance tomcat1 from the web GUI 
http://aa.bb.cc:3000/balancer-manager 
        - enter e.g. tomcat2 in the "Route Redirect" form field.
        - on submit, the respective worker is marked with "RouteRedir=tomcat2" 
in the worker list.
         
        Our problem is, requests without a session id still get routed to 
worker tomcat1 (as well as to the other 3 instances). 
         
        We use [Server Version: Apache/2.2.3 (Linux/SUSE)] in our production 
env, but I also tried [Server Version: Apache/2.2.11 (Win32)]
        The result is the same in both setups.
         
                Am I missing something essential?

You have to also "disable" the route that you are re-directing. AFAIK, it works 
like this:

Disable only: labelled requests for that route get "server unavailable", 
unlabelled requests will go to other routes.
Redirect only: labelled requests for that route get redirected, unlabelled 
requests can go to any route, including this one (this is your case).
Redirect and disable: labelled requests for that route get redirected, 
unlabelled requests will go to other routes.

Rgds,
Owen Boyle
Disclaimer: Any disclaimer attached to this message may be ignored. 




         
                Cheers
        Jürgen 
 
This message is for the named person's use only. It may contain confidential, 
proprietary or legally privileged information. If you receive this message in 
error, please notify the sender urgently and then immediately delete the 
message and any copies of it from your system. Please also immediately destroy 
any hardcopies of the message. 
The sender's company reserves the right to monitor all e-mail communications 
through their networks.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
   "   from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Reply via email to