This section covers different runtime errors that may be diagnosed using AggreGate Server logging facility or system events.
Unable to create new native thread
This message means that operating system does not allow Java Virtual Machine to create a new thread. There are several solutions for this problem:
| • | Decrease maximum memory available to JVM (JVM heap size). This increases memory available for individual threads. |
| • | Decrease thread stack size. |
| • | Switch to a 64-bit operating system and Java virtual machine. |
Out Of Memory Error: Java Heap Space
This error means that your Java Virtual Machine has run out of memory. The solution is to increase maximum memory available to JVM.
Out Of Memory Error: PermGen Space
This error means that your Java Virtual Machine is out of memory for storing loaded classes. The solution is to increase value of -XX:MaxPermSize parameter in server launcher properties files.
AggreGate Server Causes High CPU Load
It may happen that AggreGate Server consumes nearly 100% of CPU time. This situation is often caused by wrong settings of different system objects, most likely short polling periods or other frequent periodic actions.
To find the root cause of high CPU load, disable system resources type-by-type. If the CPU load decreases to the normal value after disabling resources of a certain type, enable them back gradually to find one those settings cause high CPU load.
| 1. | Suspend all devices. Synchronization settings of a device may cause frequent polling that consumes a lot of CPU time. |
| 2. | Disable all alerts. Some alert's trigger may have too short check period or refer an expensive operation (such as a query). |
| 3. | Disable all trackers. One of them may be calculated too often or refer an expensive operation. |
| 4. | Disable all scheduled jobs. A job may have triggers that cause its too frequent execution, or the job itself may consume a lot of CPU time even if executing only once. |
| 5. | Disable all widgets. Despite widget is running on a client computer, it may refer some expensive server-side operations, causing high CPU load. |
|
It may be hard to control the server under heavy CPU load. To avoid that, try starting AggreGate Server in safe mode. Delete or fix resources that consume CPU power and restart the server in normal mode. |
