Difference between revisions of "Heartbeat Check"
imported>Aeric |
imported>Aeric |
||
| Line 4: | Line 4: | ||
{{Note | If Tomcat runs out of memory is not responding for some other reason, you won't be able to tell by monitoring the port or the process. The Heartbeat Check is the only way to know.}} | {{Note | If Tomcat runs out of memory is not responding for some other reason, you won't be able to tell by monitoring the port or the process. The Heartbeat Check is the only way to know.}} | ||
If you happen to be logged in, you can visit <tt>https:// | If you happen to be logged in, you can visit <tt>https://{yourDomain}/networking/rest</tt> in your browser. If Tomcat is running, you get a list of REST APIs supported by the platform. | ||
To run the same test without logging in, use a REST client to visit the URL and specify the HEAD method (rather than GET, PUT, or POST). If Tomcat is running, you get an <tt>http</tt> return code of 200.<noinclude> | To run the same test without logging in, use a REST client to visit the URL and specify the HEAD method (rather than GET, PUT, or POST). If Tomcat is running, you get an <tt>http</tt> return code of 200.<noinclude> | ||
Latest revision as of 23:25, 10 March 2015
The Heartbeat Check checks to make sure that the platform is still running. It's accomplished by visiting a URL which gets processed by Tomcat. (This lightweight URL gets an gets an immediate response from Tomcat, if it is running.)
Note: If Tomcat runs out of memory is not responding for some other reason, you won't be able to tell by monitoring the port or the process. The Heartbeat Check is the only way to know.
If you happen to be logged in, you can visit https://{yourDomain}/networking/rest in your browser. If Tomcat is running, you get a list of REST APIs supported by the platform.
To run the same test without logging in, use a REST client to visit the URL and specify the HEAD method (rather than GET, PUT, or POST). If Tomcat is running, you get an http return code of 200.