# Gatling reports shows a request with response that never happened to server **URL:** \ **Category:** Gatling (Open-Source)\ **Tags:** gatling-academy\ **Created:** [January 11, 2023, 6:00pm UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509 "2023-01-11T18:00:00Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![Vhrlrng](https://avatars.discourse-cdn.com/v4/letter/v/d07c76/32.png) [@Vhrlrng](https://community.gatling.io/u/Vhrlrng)\ **Post date:** [January 11, 2023, 6:00pm UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/1 "2023-01-11T18:00:00Z")
Hello There, Need a help from you. I saw something strange in my Gatling test, where the Gatling report is showing a one request took max time of 20 secs response but when I try to see the same call/request in the logging or monitoring tool, that call never happened to the server. In fact, I observed this happened for couple of requests. I verified thoroughly(including graphs) during the test time frame but no trace found at all. Just wondering what could be reason. Thank you 😊 ---
**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\ **Post date:** [January 11, 2023, 9:33pm UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/2 "2023-01-11T21:33:25Z")
What’s the status of this request? Are you sure it’s not a connection or TLS handshake timeout? If that’s the case, it’s obviously not visible in the server logs as it never made it there through the network. ---
**Author:** ![Vhrlrng](https://avatars.discourse-cdn.com/v4/letter/v/d07c76/32.png) [@Vhrlrng](https://community.gatling.io/u/Vhrlrng)\ **Post date:** [January 12, 2023, 2:16am UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/3 "2023-01-12T02:16:10Z")
@slandelle The request is successfully executed with response code 200. We are actually using Datadog for app server and AppD for DB monitoring. Is it possible that request took 100% of execution time from DB hence I’m not seeing this in app server logs? ---
**Author:** ![GeMi](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/gemi/32/939_2.png) [@GeMi](https://community.gatling.io/u/GeMi)\ **Post date:** [January 12, 2023, 8:42am UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/4 "2023-01-12T08:42:02Z")
I think that you have cached this request: By default, Gatling caches responses based on: - Expires header - Cache-Control header - Last-Modified header - ETag You can disable this feature. > **[HTTP Protocol](https://gatling.io/docs/gatling/reference/current/http/protocol/#disablecaching)** > > How to configure Gatling HTTP behavior such as baseUrl, common HTTP headers, common HTTP checks and connection pool sharing. ---
**Author:** ![Vhrlrng](https://avatars.discourse-cdn.com/v4/letter/v/d07c76/32.png) [@Vhrlrng](https://community.gatling.io/u/Vhrlrng)\ **Post date:** [January 12, 2023, 9:29am UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/5 "2023-01-12T09:29:53Z")
@GeMi - I am sorry I didn’t understand much from it. Can you please elaborate! And, I already have “ **flusHttpCache** ” and “ **flushSessionCookies** ” in scripts. Please let me if I need to add anything else which helps to avoid the issue. Thanks ---
**Author:** ![GeMi](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/gemi/32/939_2.png) [@GeMi](https://community.gatling.io/u/GeMi)\ **Post date:** [January 12, 2023, 10:12am UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/6 "2023-01-12T10:12:14Z")
Do you have: ```auto http.disableCaching(); ``` in your `HttpProtocolBuilder` instance ? ---
**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\ **Post date:** [January 12, 2023, 10:32am UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/7 "2023-01-12T10:32:24Z")
This sentence is very confusing: > Gatling report is showing a one request took max time of 20 secs response but when I try to see the same call/request in the logging or monitoring tool, that call never happened to the server. @Vhrlrng Do you mean that: 1. you haven’t found a request with a 20s response time in your server logs/monitoring? 2. you identified the specific request execution (timestamp, parameters) that took 20s and couldn’t find it in your server logs/monitoring? I suspect it’s 1. In this case, you have to understand that the client side response time is not equal to the server side one: - lag in your load generator machine (ex: running on Windows with antivirus on 🤦‍♂️, saturated CPU, not enough cores ) - DNS - TCP connection - TLS handshake - network hiccup - load balancers/reverse proxies You won’t find any of those in your server side monitoring. ---
**Author:** ![Vhrlrng](https://avatars.discourse-cdn.com/v4/letter/v/d07c76/32.png) [@Vhrlrng](https://community.gatling.io/u/Vhrlrng)\ **Post date:** [January 12, 2023, 11:09am UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/8 "2023-01-12T11:09:23Z")
No @GeMi. will add that as needed. > [@GeMi](#): > > I think that you have cached this request: So, 2 or more requests were added up and showed as the single request! ---
**Author:** ![Vhrlrng](https://avatars.discourse-cdn.com/v4/letter/v/d07c76/32.png) [@Vhrlrng](https://community.gatling.io/u/Vhrlrng)\ **Post date:** [January 12, 2023, 11:15am UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/9 "2023-01-12T11:15:09Z")
> [@slandelle](#): > > - you haven’t found a request with a 20s response time in your server logs/monitoring? > - you identified the specific request execution (timestamp, parameters) that took 20s and couldn’t find it in your server logs/monitoring? Correct. @slandelle > [@slandelle](#): > > In this case, you have to understand that the client side response time is not equal to the server side one: True and I am trying to find more possible reason. 🙂 Thank you. ---
**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\ **Post date:** [January 12, 2023, 12:01pm UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/10 "2023-01-12T12:01:37Z")
> Correct. @slandelle My sentence was a XOR: 1 XOR 2, not both. > you identified the specific request execution (timestamp, parameters) that took 20s and couldn’t find it in your server logs/monitoring? So you’re saying that Gatling logged a request that received a response with a 200 that you could not find in the server logs nor monitoring?! The only way this is possible is that the response was served by a cache in front of what you’re monitoring, or that your monitoring is buggy/misses some requests. Sorry, but that’s not something we can help with, all the more without you providing a way for us to reproduce on our side. But I’m 100% convinced the issue is not on Gatling’s side. ---
**Author:** ![Vhrlrng](https://avatars.discourse-cdn.com/v4/letter/v/d07c76/32.png) [@Vhrlrng](https://community.gatling.io/u/Vhrlrng)\ **Post date:** [January 16, 2023, 6:31am UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/11 "2023-01-16T06:31:24Z")
Hi @GeMi - I did implemented this in my simulation and see still issue is persist. ![image](https://europe1.discourse-cdn.com/flex013/uploads/gatling2/original/2X/1/1f9d59e0dc3c893a79d1df9bba8566f1767b49ba.png) would you mind take a look at it! Thanks ---
**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\ **Post date:** [January 16, 2023, 7:13am UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/12 "2023-01-16T07:13:02Z")
@Vhrlrng I understand that @GeMi 's suggestion was more convenient for you so you wanted to give it a try instead of mine, but it’s wrong. It would explain requests being skipped (because cached), not long requests not visible in your server logs. ---
**Author:** ![Vhrlrng](https://avatars.discourse-cdn.com/v4/letter/v/d07c76/32.png) [@Vhrlrng](https://community.gatling.io/u/Vhrlrng)\ **Post date:** [January 16, 2023, 7:24am UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/13 "2023-01-16T07:24:17Z")
@slandelle - I am trying all the ways to understand the issue as I have very less time either to resolve or explain my team that why it occurred. Also, working with APM team to verify if monitoring tool is not capturing everything as it shows in Gatling,. Thanks ---
**Author:** ![GeMi](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/gemi/32/939_2.png) [@GeMi](https://community.gatling.io/u/GeMi)\ **Post date:** [January 16, 2023, 12:19pm UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/14 "2023-01-16T12:19:52Z")
I think you have here 2 additional options: - Run tests by any proxy and check if all requests go by it, - Install Wireshark or any tcpdump tool to check trafic durning test. ---
**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/gatling2/original/2X/b/b148e0742de35c6280726cabf3ecd3de2d320f63.png) [@system](https://community.gatling.io/u/system)\ **Post date:** [February 15, 2023, 12:20pm UTC](https://community.gatling.io/t/gatling-reports-shows-a-request-with-response-that-never-happened-to-server/7509/15 "2023-02-15T12:20:33Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.