|Knowledge base: Apia | Language: English | History ||
[ ATI00174 ] Settings of Apache Tomcat's memory to use the migrator
SummaryIf the number of objects to migrate is large, the memory required by Apia's migrator may exceede the limit of the memory of the JVM executed inside the context of an Apache Tomcat. The steps to follow in order to modify the limits of memory assignation are described in this document.
It is applied to
If problems appear when trying to carry out a migration in Apia, the first step to follow is to verify the Logs of the Apache Tomcat and Apia in search of exceptos of type java.lang.OutOfMemoryError.
If there is a register of this exception in the Log, the steps detailed hereunder must be followed.
Note: the port of the JmxRemote can be defined with any free port in the server.
2 - Start from a machine with access to the server, the jconsole.exe avaiable in the folder bin of the jsdk1.5. To connect the console to the agent enter the ip of the server and the port (8500).
In the section "Memory" there is a graphic in real time of use of memory.
Entrance in the Log: java.lang.OutOfMemoryError: PermGen space error
Entrance in the Log: java.lang.OutOfMemoryError: Java heap space error
Note: the values are given as an example. They must adjust to the values monitored by the jconsole.
4 - Add in the key [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\NameContext\Parameters\Java] inside the Value Options the values indicated in point 3.
Restart the Apache Tomcat's service so that it takes the changes.
5 - Execute from step 3 until achieving values which allow the correct execution of the migration.
6 - Once the migration has been executed successfully, reestablish the values by default.
Note: it is suggested the use of the jconsole to adjust the values by default, so that they allow a correct use of the system without overassigning resources of the server.