Difference between revisions of "Heartbeat Check"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
<includeonly>=== Heartbeat Check===</includeonly>
<includeonly>=== Heartbeat Check===</includeonly>
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. (The URL is very lightweight, does not require a login, and still gets processed by Tomcat.)
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.)
:<pre>https://<yourdomain>/networking/rest</pre>


If Tomcat is running, you will get an <tt>http</tt> return code of 200.
{{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://{yourDomain}/networking/rest</tt> in your browser. If Tomcat is running, you get a list of REST APIs supported by the platform.
<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>


[[Category:Installation]]
[[Category:Installable Version]]
</noinclude>
</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.)

Notepad.png

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.