I'd go with your HTTPAPI option....most "web monitoring" solutions I've
seen do so by sending a test http request.


On Fri, Mar 7, 2014 at 1:07 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

I've been asked to come up with a command-line (or batch job) utility to
check, programmatically, whether a Tomcat context that's part of one of
our products is alive and accepting connections, or hung.

I'm already attempting to pick the brains of our people who developed
the Tomcat context, to see what they can recommend I do.

But I'd like the Midrange List's input as well. One idea I had, since we
bundle HTTPAPIR4 with the product, was to send test requests to the
context via HTTPAPI.

Another idea I've had would be to run some sort of headless test Java

Any suggestions?

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact