>> Dear André, >> >> thank you for quickly announcing your idea for an workaround. But you right >> see the limits, and the more important >impact of disabling the connectors is that it will also disable the traffic to >all the other running applications (and we have a >bunch of it on each of our Tomcats) >> >> In the first instance I want to have a fix for the issue. But nevertheless, >> maybe this lead me to a suitable workaround if I >think about it in the background. >> > >Well, here is a little variation of the idea then : >The purpose of the monitoring is normally to verify that the applications are >responding, >right ? (*) >And the fact that the applications are responding, does not depend on the >Connector >through which such requests come in, right ? >So why not define an additional Connector, on a different port, for usage >*only* by the >monitoring system, and disable only /that/ Connector while you are doing your >application >update ? > >(*) I mean, if you want to verify that the connection is working, then you can >just do a >"ping" kind of test.
Dear André, So why? It's because want to modify a complex, multi-staged and well-working platform as a last resort only. The monitoring does a lot more than to verify that the applications are running, it's uses a bunch of the data available via the MBeans for a control dashboard. It's was my mistake to use the term workaround ... Guido --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
