On 13.07.2016 15:51, Jäkel, Guido wrote:
So it would appear that if the Connectors are disabled, the monitoring system
is not able
to reach Tomcat, and the problem does not occur then.
So would it not be possible to create some little piece of software, which would
temporarily "suspend" or "disable" the Connectors, while the application update
is taking
place, and then re-enable them when it's done ?
Of course, if the application update is also going though the Connectors, this
may be a
problem..
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
