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
There's a race condition between the thread that's waiting for Tomcat to become inactive or the graceful shutdown to be aborted and the thread that aborts the shutdown and stops Tomcat when the grace period has elapsed. This race can lead to Tomcat appearing to have become inactive before the abort of the shutdown is noticed. When this happens, the result of the shutdown is reported as IDLE when it should have been REQUESTS_ACTIVE. This result is mostly benign although it does affect the log messages that are emitted. It is also causing some of our graceful shutdown tests to be flaky.
The text was updated successfully, but these errors were encountered:
This only affects 3.1.x (and earlier, now unsupported branches) as the problem was addressed in 3.2 as a side-effect of the changes to separate stop and destroy.
While the bug fixed in 3.1.x (gh-39942) has already been addressed as
a side-effect of the changes made in dbb2428, the change is merged
forwards here to improve the consistency of the code between branches.
There's a race condition between the thread that's waiting for Tomcat to become inactive or the graceful shutdown to be aborted and the thread that aborts the shutdown and stops Tomcat when the grace period has elapsed. This race can lead to Tomcat appearing to have become inactive before the abort of the shutdown is noticed. When this happens, the result of the shutdown is reported as
IDLE
when it should have beenREQUESTS_ACTIVE
. This result is mostly benign although it does affect the log messages that are emitted. It is also causing some of our graceful shutdown tests to be flaky.The text was updated successfully, but these errors were encountered: