Hi Sticky Session : We do not use Cookie in our Existing applications and the same is configured to work perfectly with "ProxyPass & ProxyPassReverse
ProxyPass /APPX http://192.168.4.32:8085/APPX ProxyPassReverse /APPX http://192.168.4.32:8085/APPX .... >>You can enable debug log level I have already done with "LogLevel error" as stated. [Mon Jun 24 03:55:06 2013] [notice] Apache/2.2.22 (Unix) DAV/2 configured -- resuming normal operations [Mon Jun 24 03:55:15 2013] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 192.168.4.32:8085 (192.168.4.32) failed [Mon Jun 24 03:55:15 2013] [error] ap_proxy_connect_backend disabling worker for (192.168.4.32) [Mon Jun 24 03:55:16 2013] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 192.168.4.32:8086 (192.168.4.32) failed [Mon Jun 24 03:55:16 2013] [error] ap_proxy_connect_backend disabling worker for (192.168.4.32) [Mon Jun 24 04:23:37 2013] [notice] caught SIGTERM, shutting down [Mon Jun 24 04:25:52 2013] [notice] Digest: generating secret for digest authentication ... [Mon Jun 24 04:25:52 2013] [notice] Digest: done [Mon Jun 24 04:25:53 2013] [notice] Apache/2.2.22 (Unix) DAV/2 configured -- resuming normal operations [Mon Jun 24 04:28:07 2013] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 192.168.4.32:8085 (192.168.4.32) failed [Mon Jun 24 04:28:07 2013] [error] ap_proxy_connect_backend disabling worker for (192.168.4.32) [Mon Jun 24 04:29:33 2013] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 192.168.4.32:8085 (192.168.4.32) failed [Mon Jun 24 04:29:33 2013] [error] ap_proxy_connect_backend disabling worker for (192.168.4.32) [Mon Jun 24 05:29:54 2013] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 192.168.4.32:8085 (192.168.4.32) failed with regards karthik On Tue, Jun 25, 2013 at 5:12 AM, Daniel Ruggeri [via Apache HTTP Server] < ml-node+s18135n5006594...@n6.nabble.com> wrote: > On 6/23/2013 11:37 PM, nskarthik wrote: > > > Hi > > > > SPEC : Apache httpd 2.22 [ Cannot upgrade currently ] > > O/s SUSE Enterprise-10 > > Sticky session [ Have 2 Tomcats with session based application ] > > > > The following is Configured with Sticky session as per APACHE Docs > > > > / > > LoadModule proxy_ajp_module modules/mod_proxy_ajp.so > > LoadModule proxy_balancer_module modules/mod_proxy_balancer.so > > LoadModule proxy_http_module modules/mod_proxy_http.so > > LoadModule ssl_module modules/mod_ssl.so > > LoadModule proxy_connect_module modules/mod_proxy_connect.so > > LoadModule proxy_ftp_module modules/mod_proxy_ftp.so > > LoadModule proxy_scgi_module modules/mod_proxy_scgi.so > > > > <Proxy balancer://myclust> > > BalancerMember http://192.168.4.32:8085 loadfactor=1 > > BalancerMember http://192.168.4.32:8086 loadfactor=1 > > ProxySet lbmethod=bytraffic > > </Proxy> > > ProxyPass /APPX balancer://myclust/ stickysession=JSESSIONID > > ProxyPassReverse /APPX balancer://myclust// > > > > Problem tried > > > > a)Application APPX is not reflected in the URL as > http://192.168.8.77/APPX > What do you mean by this? According to your requirements, should it be? > I do see that you have a trailing slash on the second argument but not > the first in ProxyPass - you should avoid this > > > b)If the BalancerMember are complete defined as "BalancerMember > > http://<IP>:<PORT>/APPX ,then the application appears in the URL > > http://192.168.8.77/APPX > > > > c)Stick Session is not maintained [ have checked the application after > > logging > > You can enable debug log level - the balancer will log whether it can > detect the sticky session cookie. > > > HTTP Status 404 - /APPX/Dashboard.action > > > > > > Am i doing something Wrong ?? > > > > > > with regards > > karthik > > > -- > Daniel Ruggeri > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden > email]<http://user/SendEmail.jtp?type=node&node=5006594&i=0> > For additional commands, e-mail: [hidden > email]<http://user/SendEmail.jtp?type=node&node=5006594&i=1> > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://apache-http-server.18135.x6.nabble.com/Proxy-Balancing-Not-working-as-Expected-tp5006568p5006594.html > To unsubscribe from Proxy Balancing Not working as Expected, click > here<http://apache-http-server.18135.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5006568&code=bnNrYXJ0aGlrLmtAZ21haWwuY29tfDUwMDY1Njh8Mjc2ODA5MTg1> > . > NAML<http://apache-http-server.18135.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- *N.S.KARTHIK R.M.S.COLONY BEHIND BANK OF INDIA R.M.V 2ND STAGE BANGALORE 560094* -- View this message in context: http://apache-http-server.18135.x6.nabble.com/Proxy-Balancing-Not-working-as-Expected-tp5006568p5006633.html Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com.
