On Wed, Aug 31, 2022 at 4:56 PM vaidya nathan <vaidyaatdst@xxxxxxxxx> wrote:
>
> Following is our setup
>
> 1. we have an angular application depoyed in apache webserver IBM HTTP Server 8.5.5.20(eqivalent apache http server 2.2.8) that talks to a spring boot server .
>
> 2. certain users are having issues when trying to communicate from the web application with the spring boot server . Other users are fine . Errors on the logs with debug option turned on as below:
>
>
>
> [Wed Aug 31 12:26:11 2022] [debug] proxy_util.c(2060): proxy: connecting {URL}/generate-token/XXX to {URL Server}:443
>
> [Wed Aug 31 12:26:11 2022] [debug] proxy_util.c(2158): [28558] proxy: connected {URL}/generate-token/XXX to {URL Server}:443
>
> [Wed Aug 31 12:26:11 2022] [debug] proxy_util.c(2321): [28558] proxy: HTTPS: fam 2 socket created to connect to {URL Server}:443
>
> [Wed Aug 31 12:26:11 2022] [debug] proxy_util.c(2345): proxy: HTTPS: fam 2 socket completed connect to {URL Server}:443 (local port 36760)
>
> [Wed Aug 31 12:26:11 2022] [debug] proxy_util.c(2435): proxy: HTTPS: connection complete to { Server Host}:443 (origin hostname '{URL Server}', local port 36760)
>
> [Wed Aug 31 12:26:11 2022] [debug] mod_proxy_http.c(1005): [client {Client URL}:52370] proxy: begin prefetch request body origin {URL1}:36760<->{URL2}:443 client {URL1}:1035<->{URL2}:52370, referer: {URL}:1035{ redirect path }
>
> [Wed Aug 31 12:26:11 2022] [debug] mod_proxy_http.c(1144): [client {Client URL}:52370] proxy: done prefetch meth=1 origin {URL1}:36760<->{URL2}:443 client {URL1}:1035<->{URL2}:52370, referer: {URL}:1035{ redirect path
>
> [Wed Aug 31 12:26:11 2022] [error] [client { Client URL }:52370] (104)Connection reset by peer: proxy: error reading status line from remote server { URL Server} , referer: { full url with redirect path }
mod_proxy made a new backend connection and was presumably able to
perform an SSL handshake. But when it went to read the response, with
no delay from when the conn was established, the connection had
already been torn down by the other side.
I don't know what IHS handshaked with here, or where the likely TCP
RST comes from, but if it's not your appserver it's something in front
of it.
You'll need to scrutinize a packet capture from around the same time.
The mod_proxy_http.c(1144): error shows you the ephemeral port used by
mod_proxy and should let you zoom in directly to the failing
connection. If the RST really comes in shortly after the encrypted
HTTP request is sent, then you're debugging the wrong system
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|