hi,

Since upgrading from HAProxy 1.8 to 2.4, access to our WebLogic 12 servers
has been performing very poorly — with longer response times and frequent
error responses.

Indeed, the WebLogic server returns the following error:

> SEVERE (05/11/2025 - 10:56:01) - Error while accessing the specific
> academic movement URL
> javax.naming.CommunicationException [Root exception is
> java.net.ConnectException: http://webservices.domain.fr:80: Bootstrap to
> webservices.domain.fr/192.168.149.123:80 failed. It is likely that the
> remote side declared peer gone on this JVM]


Our HAProxy configuration is in *HTTP mode*, as shown below:

#---------------------------------------------------------------------
> # Global settings
> #---------------------------------------------------------------------
> global
>     log         127.0.0.1  local0 debug
>     chroot      /var/lib/haproxy
>     pidfile     /var/run/haproxy.pid
>     maxconn     8000
>     user        haproxy
>     group       haproxy
>     daemon
>     #tune.bufsize            32768
>     tune.bufsize            65536
>     tune.maxrewrite         16384
>     tune.ssl.default-dh-param 2048
>     stats socket /var/lib/haproxy/stats
>
> defaults
>     mode                    http
>     log                     global
>     option                  dontlognull
>     log-format "%ci:%cp [%tr] %ft %b/%s %TR/%Tw/%Tc/%Tr/%Ta %ST %B %CC %CS
> %tsc %ac/%fc/%bc/%sc/%rc %sq/%bq %hr %hs %{+Q}r"
>     option                  dontlognull
>     option forwardfor       except 127.0.0.0/8
>     option                  redispatch
>     retries                 0
>     timeout http-request    5m
>     timeout queue           3m
>     timeout connect         5m
>     timeout client          5m
>     timeout server          5m
>     timeout http-keep-alive 100s
>     timeout check           100s
>     maxconn                 8000
>
> frontend f_192_168_149_101_80
>    bind 192.168.149.101:80
>    mode http
>    http-request capture req.hdr(Host) len 80
>    option forwardfor
>    option http-no-delay
>    option accept-invalid-http-request
>    acl weblo path_beg -i /fia_wls_internal
>    use_backend b_webservices_weblo if weblo
>    default_backend b_webservices
>
> #==========================
> # BACKEND WEBLO : weblo
> #==========================
> backend b_webservices_weblo
>    no option http-pretend-keepalive
>    balance source
>    #balance roundrobin
>    mode http
>    http-reuse safe
>    option http-keep-alive
>    timeout connect 5s
>    timeout server 1h
>    timeout http-keep-alive 1h
>    ###
>    option forwardfor
>    option accept-invalid-http-response
>    stick-table type string len 64 size 10k expire 12h
>    stick on cookie(JSESSIONID)
>    stick on cookie(PHPSESSID)
>    cookie SRV_WEBSERVICES insert indirect nocache
>    server web1 192.168.149.123:80 cookie web1 check weight 1 maxconn 3000
>    server web2 192.168.149.129:80 cookie web2 check weight 1 maxconn 3000
>

 Here’s a quick overview of the infrastructure:

HAProxy 2.4 ------- Apache 2.4 ------- WebLogic 12.2


We have tried several changes to the http-reuse setting, switching between
never and safe, removed the option http-server-close, and added keepalive,
but nothing seems to work.

We would be very grateful for your help.

Best regards,
Karim

Reply via email to