[ https://issues.apache.org/jira/browse/DISPATCH-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ganesh Murthy resolved DISPATCH-1931. ------------------------------------- Resolution: Cannot Reproduce > HTTP client not seeing a reply when sending a request through the TCP adaptor > ----------------------------------------------------------------------------- > > Key: DISPATCH-1931 > URL: https://issues.apache.org/jira/browse/DISPATCH-1931 > Project: Qpid Dispatch > Issue Type: Bug > Components: Protocol Adaptors > Reporter: Fernando Giorgetti > Assignee: Michael Goulish > Priority: Major > Fix For: 1.18.0 > > Attachments: private-router.log, public-router.log, routerLinks.out, > successful-client-sample.log, tcpConnectors.out, tcpListeners.out > > > In a two router topology (using Skupper on Kubernetes), an HTTP client (curl) > was not > seeing any response from the routers for requests going through a TCP > adaptor. > The request was reaching the router that has the TCP connector to the HTTP > Server, > but the request was not reaching the HTTP server and the HTTP client is > being disconnected > with no reply from the router. > I have also executed the HTTP client (curl) from inside the router container, > to avoid issues > with the Kubernetes service and observed the same outcome. > The TCP Listener that was causing issues was: nginx-2-svc-exp-notarget port > 1026 (from router named private-annotated-1-skupper-router-746455769d-jcmmh). > > {noformat} > [root@skupper-service-controller-78747bf9b6-xwclq app]# curl --trace > /tmp/curl.error nginx-2-svc-exp-notarget:8080 > curl: (52) Empty reply from server > [root@skupper-service-controller-78747bf9b6-xwclq app]# cat /tmp/curl.error > == Info: Rebuilt URL to: nginx-2-svc-exp-notarget:8080/ > == Info: Trying 10.111.1.35... > == Info: TCP_NODELAY set > == Info: Connected to nginx-2-svc-exp-notarget (10.111.1.35) port 8080 (#0) > => Send header, 93 bytes (0x5d) > 0000: 47 45 54 20 2f 20 48 54 54 50 2f 31 2e 31 0d 0a GET / HTTP/1.1.. > 0010: 48 6f 73 74 3a 20 6e 67 69 6e 78 2d 32 2d 73 76 Host: nginx-2-sv > 0020: 63 2d 65 78 70 2d 6e 6f 74 61 72 67 65 74 3a 38 c-exp-notarget:8 > 0030: 30 38 30 0d 0a 55 73 65 72 2d 41 67 65 6e 74 3a 080..User-Agent: > 0040: 20 63 75 72 6c 2f 37 2e 36 31 2e 31 0d 0a 41 63 curl/7.61.1..Ac > 0050: 63 65 70 74 3a 20 2a 2f 2a 0d 0a 0d 0a cept: */*.... > == Info: Empty reply from server > == Info: Connection #0 to host nginx-2-svc-exp-notarget left intact{noformat} > > Or when executed directly from the router pod: > {noformat} > [root@skupper-router-746455769d-jcmmh bin]# curl --trace - 0.0.0.0:1026 > == Info: Trying 0.0.0.0:1026... > == Info: TCP_NODELAY set > == Info: Connected to 0.0.0.0 (127.0.0.1) port 1026 (#0) > => Send header, 76 bytes (0x4c) > 0000: 47 45 54 20 2f 20 48 54 54 50 2f 31 2e 31 0d 0a GET / HTTP/1.1.. > 0010: 48 6f 73 74 3a 20 30 2e 30 2e 30 2e 30 3a 31 30 Host: 0.0.0.0:10 > 0020: 32 36 0d 0a 55 73 65 72 2d 41 67 65 6e 74 3a 20 26..User-Agent: > 0030: 63 75 72 6c 2f 37 2e 36 35 2e 33 0d 0a 41 63 63 curl/7.65.3..Acc > 0040: 65 70 74 3a 20 2a 2f 2a 0d 0a 0d 0a ept: */*.... > == Info: Recv failure: Connection reset by peer > == Info: Closing connection 0 > curl: (56) Recv failure: Connection reset by peer{noformat} > I am attaching some other logs from both routers to help with the > investigation. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org