on Jun 14, 2016Article Content
| Article Number | 000028841 |
| Applies To | Affected Versions: 3.6.X |
| Resolution | Memory exceptions can sometimes be caused by a lack of configured memory for the AveksaAgent. To fix this increase the memory on the agent using the following process: 1. On the ACM appliance, logged in as the oracle user go to the directory AveksaAgent/conf $ cd /home/oracle/AveksaAgent/conf 2. Look for a file called wrapper.conf in that directory 3. Open the file (using your preferred editor) and look for the variables: wrapper.java.initmemory and wrapper.java.maxmemory. By default they are set to 128 and 256 4. Change these settings to 256 and 512 to increase min and max memory 5. Re-start the agent sudo service aveksa_agent stop sudo service aveksa_agent start 6. To verify that the new settings took effect execute the following from the UNIX command line: ps -ef | grep Boot This should show the agent process. You should see a line something like the one below .The data in RED indicates that the memory has been increased. oracle 19226 19224 7 00:34 ? 00:00:01 /usr/bin/jdk1.5.0_06/bin/java -Dagent.home=.. -Djava.endorsed.dirs=../common/endorsed -Xms256m -Xmx512m -Djava.library.path=../agent/lib -classpath ../agent/lib/wrapper.jar:../agent/lib/bootstrap.jar:../common/lib/log4j-1.2.9.jar:../conf -Dwrapper.key=seVkK80NVoRf0CVp -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=19224 -Dwrapper.version=3.2.0 -Dwrapper.native_library=wrapper -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp com.aveksa.client.datacollector.startup.Bootstrap start NOTE: If these settings don’t solve the problem try increasing the memory using min 384 and max 768. |