Hi,

Your server definition is wrong:
server  portal 192.168.52.73:8080/HelloVivi cookie A check inter 2000
rise 2 fall 5
server  portal 192.168.52.72:8080/HelloVivi cookie A check inter 2000
rise 2 fall 5

should be something like this:
server  portalA 192.168.52.72:8080 cookie A check inter 2000 rise 2 fall 5
server  portalB 192.168.52.73:8080 cookie B check inter 2000 rise 2 fall 5

If you mandatory need to prefix all URLs by HelloVivi, then you can
add it with reqirep:
reqrep ^([^\ :]*)\ /(.*)     \1\ /HelloVivi/\2

Baptiste


On Thu, Nov 1, 2012 at 11:51 PM, Viviana Cuellar Rivera
<[email protected]> wrote:
> Hi, I have two balancers that connect to 4 servers JBOSS, the DIEA is
> something like the following:
>                                                    _JBOSS1
>                       balancer 1 ------ |
>                                                   |_JBOSS2
>
>                                                    _JBOSS1
>                       balancer 2 ------ |
>                                                   |_JBOSS2
>
>
> so what I have currently implemented:
>                                                    _JBOSS1
> apache1 mod balancer ------ |
>                                                   |_JBOSS2
>
>                                                    _JBOSS1
> apache1 mod balancer ------ |
>                                                   |_JBOSS2
>
> Hi, I have two balancers that connect to 4 servers JBOSS, the idea is
> something like the following:
>
> so what I have currently implemented:
>
> apache1 balancer ------ |
>
> And I want to change the layer integrated with Apache by HAProxy keepalived,
> reaching a high availability scheme because at the time my apache servers do
> not have high availability mechanisms.
>
>
> The problem I find is the initial testing of safety and do not know how to
> configure it to publish just a page, for example, that only access the page
> Hello Vivi, not all content that is hosting the server because if I enter
> the 192.168.52.40/jmx-console direction, enters the JBoss console and if I
> enter the address 192.168.52.40 access the home page of JBOSS, and that is
> not a content that I post, someone can explain how to do it?
>
> Besides the problem I see it as something serious is that the connection
> between HAProxy and JBOSS not in ssh, how to do that?
>
> This is my current setup:
> global
> log 127.0.0.1 local0
> log 127.0.0.1 local1 notice
> #log loghost local0 info
> maxconn 5000
> #chroot  /var/lib/haproxy
>         pidfile /var/run/haproxy.pid
> user haproxy
> group haproxy
> daemon
> #debug
> #quiet
>
> defaults
> log global
> mode http
> option httplog
> option dontlognull
> option httpclose
> option forwardfor
> retries 3
> option redispatch
> maxconn 5000
> contimeout 10000 # por defecto 10 seg de time out si no es encontrado un
> serverweb
> clitimeout 500000
> srvtimeout 500000
>
>
> listen webfarm 192.168.52.40:80
> mode http
> cookie JSESSIONID prefix
> #cookie SERVERID insert indirect
> balance roundrobin
> #balance source
> stats enable
> stats auth tesis:123456 # login:contraseƱa
> option httpclose # disable keep-alive
> option forwardfor
> option httpchk HEAD /Health_Check123 HTTP/1.0
>         server portal 192.168.52.73:8080/HelloVivi cookie A check inter 2000
> rise 2 fall 5
>         server portal 192.168.52.72:8080/HelloVivi cookie A check inter 2000
> rise 2 fall 5
>
> #rspidel ^Set-cookie:\ IP= # do not let this cookie tell our internal IP
> address
> #errorfile 400 /etc/haproxy/errors/400.http
> #errorfile 403 /etc/haproxy/errors/403.http
> #errorfile 408 /etc/haproxy/errors/408.http
> #errorfile 500 /etc/haproxy/errors/500.http
> errorfile 502 /etc/haproxy/errors/502.http
> errorfile 503 /etc/haproxy/errors/503.http
> errorfile 504 /etc/haproxy/errors/504.http
>
> PS: I apologize for my English
>

Reply via email to