AggreGate Server may show an error message on startup or appear to start successfully but not accept incoming connections from Device Servers or clients. This probably means there were some serious or critical errors during server startup. Check AggreGate Server log file to find out the actual reason of error. By default, this file is called server.log and it is located in AggreGate Server installation directory. See Configuring Logging section for more information about logging.
Sometimes critical errors displayed in the error dialog are caused by some smaller problem that can be traced back using the log file.
The JVM could not be started. The main method could have thrown an exception.
This message means a critical error occurred during JVM startup. To see the exact error message that should give troubleshooting hints use ag_server_console launcher to start AggreGate Server.
|
Under Windows, the console window may disappear before you read the message. In this case, use command line interpreter to start ag_server_console. For that, go to Start Menu > Run, type cmd and click OK. The command line interpreter window will open. Now type %path_to_AggreGate Server%/ag_server_console to start the launcher. |
Could not reserve enough space for object heap
You may see the following message when trying to start AggreGate Server:
Error occurred during initialization of VM
Could not reserve enough space for object heap
The JVM could not be started. The main method may have thrown an exception.
It means that the Java Virtual Machine cannot allocate the amount of memory specified by -Xmx (maximum memory) launcher file parameter in a single contiguous block. There are several possible solutions:
| • | Decrease the value of -Xmx parameter if your AggreGate Server is not under a hard load |
| • | Try to free up some memory by unloading the applications of rebooting the machine |
| • | Add more RAM to the machine AggreGate Server is running on |
| • | Under Windows, some applications may register their dynamic libraries (DLLs) to be located in memory at a certain absolute address. This separates the memory into several blocks and does not allow the AggreGate Server JVM to allocate a large single block of memory. To fix that, use a registry editor to remove all entries from HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Windows\AppInit_DLLs. Be sure to make a backup first! |
Error starting database service
This error means that server was not able to establish connection with the database. Normally the root cause of the error is appended to the error message. If the root cause cannot be identified by reading server startup error message, try the following:
| • | Disable database connection pooling |
| • | Try starting the server and wait until error message pops up |
| • | Browse the end of server log file (server.log by default) to find out the root cause of database problems |
| • | If you're using the bundled MySQL database, it is likely that MySQL service failed to start. Check %aggregate_folder%\mysql\data\*.err files for errors. Since bundled MySQL server is configured for high performance, it may not be able to allocate enough buffer memory on some PCs. In this case, decrease values of innodb_buffer_pool_size and innodb_buffer_pool_size parameters in MySQL configuration file (%aggregate_folder%\mysql\my.ini). |
Server Was Started But Clients Cannot Connect
If AggreGate Server was launched but it's not possible to connect to it using AggreGate Client and Web Desktop, it may happen that server startup is still in progress. Check server log file (server.log) to see whether the server is executing a long operation, such as database maintenance. Please contact Tibbo technical support if server startup is regularly taking longer than 3-5 minutes.