405 Method is not Allowed exception: "Request Method 'T' not supported" for GET call and "Request Method 'ST' not supported" for POST

[manuj20]

Hi Team,
I am facing a very strange issue in my project. It is related to rest API call using spring reactive webclient bulider. It is working fine on local and prod as well but abnormally giving below error after 3 or 4 request to same endpoint.
"org.springframework.web.server.MethodNotAllowedException: 405 METHOD_NOT_ALLOWED "Request method 'T' not supported"
This is valid exception as method going to "T" for Get method and "ST" for Post method .I am not able to understand why two starting charcter truncating from method name

Please help me resolve this error.

[sbrannen]

Can you please provide a minimal sample application that reproduces the issue (preferably a project that we can check out from a Git repository or a complete zip file).

Thanks

[manuj20]

It is not reproducible on Local .We are getting this abnormal behaviour on production sometime not everytime .For 1 request out of 5 for same during load testing. We try to reproduce it on local.But We can't.

[bclozel]

From your description, it’s not clear if the issue comes from the client or the server.
Spring is not involved directly in writing or reading the HTTP protocol, so this might be a problem with the server/client library, or more likely a concurrency issue with your own code.

I’m closing this issue for now as there is no way to make progress with so little information.
Feel free to reopen this issue when you’ll manage to reproduce the problem in a minimal (this is important) application. To reproduce this locally, maybe you could try and simulate concurrency with multiple concurrent requests to your service (try the « ab » tool for example).

Thanks!

[rohan-new]

@manuj20 Were you able to resolve the issue ? As I am facing the same issue of getting 405 method not allowed on subsequent api calls using webclient.

[manuj20]

@rohan-new We are not able to resolve this issue as per my knowledge...as it was happening with probability 1 out 20...so reproduce it difficult we carry forward this error by customised webclient connection pool configuration...We did just this but that doesn't seems to me solution . . So you can carry forward with this thread by reopening it