| Related Documentation | \nVersion of up.time \naffected | \nAffected Platforms | \n
| IOException: Not enough space (Java heap) \n | v7.0 and earlier | \nAll | \n
...
...
| Warning |
|---|
| The following information is applicable to earlier versions of |
...
| Uptime Infrastructure Monitor. |
...
| If you are using |
...
| Uptime Infrastructure Monitor 7.X, refer to the |
...
| Uptime Infrastructure Monitor product documentation for the latest information. |
...
The Java heap is a repository for Java objects and free memory. The Java heap size should generally be increased when you have:
...
- A large number of service monitors.
- A large number of reports to run.
...
Adjusting the Java Heap Size
...
uptime is installed with a default Java Heap Size value of 1 Gb. For optimal performance, a value of 1.5 Gb is usually recommended.
...
| Note |
|---|
| When increasing the Java Heap Size, ensure that the Operating System can support the new setting. If the OS does not have the desired amount of memory available exclusively for |
...
| Uptime Infrastructure Monitor, the |
...
| Uptime Infrastructure Monitor core will fail on startup. |
...
RedHat, SuSE and Solaris Monitoring Stations
...
To change the Java Heap Size, modify the <uptime install dir>/uptime.lax (or uptime4d.lax in up.time Uptime Infrastructure Monitor 4) file to look like this:
...
| Note |
|---|
| Java Heap Size is measured in bytes on UNIX and Linux systems. |
...
| No Format |
|---|
# LAX.NL.JAVA.OPTION.JAVA.HEAP. SIZE.MAX |
...
# -------------------------------------- |
...
# Max VM size in bytes |
...
lax.nl.java.option.java.heap.size.max=1500m |
...
...
Windows Monitoring Station
...
To change the Java Heap Size on a Windows system, edit the following line in the <uptime install dir>/wrapper.conf file:
...
| Note |
|---|
...
| Java Heap Size is measured in megabytes on Windows systems. |
...
| No Format |
|---|
wrapper.java.maxmemory=1500 |
...