|
|
|||||
|
|
|
||||
| At line 10 changed 1 line. |
| Current version: 0.99 |
| Current version: 1.42 |
| At line 68 changed 3 lines. |
| * Failover is initiated in under 40 seconds by Metawerx Monitoring if your JVM process is not running |
| * Failover is initiated in under 90 seconds (to allow for false positives) by Metawerx Monitoring if your JVM process does not return a standard HTTP response, or the text you have specified in the first 10k of the response |
| * Failback is initiated as soon as Metawerx Monitoring notices your JVM is responding again |
| * Failover is initiated in under 2 seconds by Metawerx Monitoring if your JVM process is not running |
| * Failover is initiated in under 60 seconds (to allow for false positives) by Metawerx Monitoring if your JVM process does not return a standard HTTP response, or the text you have specified in the first 10k of the response |
| * Your JVM resource usage and logs are scanned every 5 seconds by Metawerx Monitoring until JVM is responding again, then requests are switched back to your JVM |
| At line 78 changed 1 line. |
| * Immediate (under 40ms) failover on JVM startup, JVM kill, or Activate Maintenance Mode commands |
| * The time taken to switch to maintenance-mode is under 40ms |
| * A new instance of your JVM is started on our HA-Cluster in under 2 seconds |
| * Your maintenance page will be displayed until your system is responsive again |
| * You are alerted on all failed startups or successful startups |
| At line 142 added 1 line. |
| \\ |
| At line 145 added 1 line. |
| \\ |
