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
A web app using the servlet stack with a separate management server will write the management server's access logs to a file prefixed with management_. When you switch to WebFlux using Jetty, Tomcat, or Undertow, the main and management servers use the same location for their access logs. The reactive side of things needs a fix that was similar to #6618, which was made before we had reactive web support.
While the two servers writing access logs to the same location is a bug, there's a small chance that it's a load-bearing bug. Given that no users have reported the problem, I'm going to fix this only in 3.5.x. We can back port the changes in the future if necessary.
The text was updated successfully, but these errors were encountered:
A web app using the servlet stack with a separate management server will write the management server's access logs to a file prefixed with
management_
. When you switch to WebFlux using Jetty, Tomcat, or Undertow, the main and management servers use the same location for their access logs. The reactive side of things needs a fix that was similar to #6618, which was made before we had reactive web support.While the two servers writing access logs to the same location is a bug, there's a small chance that it's a load-bearing bug. Given that no users have reported the problem, I'm going to fix this only in 3.5.x. We can back port the changes in the future if necessary.
The text was updated successfully, but these errors were encountered: