You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are facing an issue where tomcat flushes authentication detail after request timeout.
On receiving a request, we call a few APIs to fetch information which sometimes takes more than 30 seconds when the API server response is slow. During that time, tomcat sends an error to the front-end system and flushes all the request parameters from the current request even though request processing is still in progress. Due to that Optional authentication = securityService.getAuthentication(); sends an empty response.
We are deploying the application War on tomcat. Also, We are not facing such a problem when we run our application with netty or embedded tomcat.
Is there any way we can avoid flushing authentication information from tomcat until request processing completes? Also, is there any best practices we should follow to prevent the such condition?
I am attaching a sample project. you can find the step to reproduce the scenario in the Readme file.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Team,
We are facing an issue where tomcat flushes authentication detail after request timeout.
On receiving a request, we call a few APIs to fetch information which sometimes takes more than 30 seconds when the API server response is slow. During that time, tomcat sends an error to the front-end system and flushes all the request parameters from the current request even though request processing is still in progress. Due to that Optional authentication = securityService.getAuthentication(); sends an empty response.
We are deploying the application War on tomcat. Also, We are not facing such a problem when we run our application with netty or embedded tomcat.
Is there any way we can avoid flushing authentication information from tomcat until request processing completes? Also, is there any best practices we should follow to prevent the such condition?
I am attaching a sample project. you can find the step to reproduce the scenario in the Readme file.
JDK Version : 11.17(Azul zulu)
Tomcat Version: 9.0.70
Micronaut Version: 3.8.1
Beta Was this translation helpful? Give feedback.
All reactions