Closed sjmittal closed 6 months ago
If I am not wrong, you have added produces("text/plain") to the POST route which means that requests that don't have header Accept with "text/plain" will not be routed to this route. First client requests probably contains this header and is able to route correctly but the second request does not contain this header which results in 404.
Thanks for pointing this out.
Questions
Looks like vertx web randomly returns 404 error under high load.
Version
4.5.7
Context
I encountered an exception which looks suspicious while running vertx web on AWS ECS and connecting to a load balancer which receives very high traffic, somewhere like 1000 requetst per second.
Do you have a reproducer?
Here is how I have configured my router:
Steps to reproduce
You can clearly see that for same path it was able to process one request but for other it simply returns a 404 error. Any reason what could be the cause.
Extra