Tomcat 7 How to set initial heap size correctly

Question

I was trying to adjust initial heap size of a tomcat 7  CentOS  java -version  1 6 0 25-b06  instance by adding the following line to catalina sh   export CATALINA OPTS  -Xms 512M -Xmx 1024M    Starting up tomcat fails and logs the following message to catalina out   Invalid initial heap size  -Xms 512m Could not create the Java virtual machine    What is wrong with these options

User · Answer

Go to  Tomcat Directory  bin directory  if Linux then create setenv sh  else if Windows then create setenv bat  content of setenv   file    export CATALINA OPTS   CATALINA OPTS -Xms512m  export CATALINA OPTS   CATALINA OPTS -Xmx8192m  export CATALINA OPTS   CATALINA OPTS -XX MaxPermSize 256m    after this restart tomcat with new params   explanation and full information is here  http   crunchify com how-to-change-jvm-heap-setting-xms-xmx-of-tomcat

User · Answer

You might no need to having export  just add this line in catalina sh    CATALINA OPTS  -Xms512M -Xmx1024M

User · Answer

It works even without using  export  keyword  This is what i have in my setenv sh   usr share tomcat7 bin setenv sh  and it works   OS   14 04 1-Ubuntu Server version  Apache Tomcat 7 0 52  Ubuntu  Server built    Jun 30 2016 01 59 37 Server number   7 0 52 0  JAVA OPTS  -Dorg apache catalina security SecurityListener UMASK  umask  -server -Xms6G -Xmx6G -Xmn1400m -XX HeapDumpPath  Some logs  -XX  HeapDumpOnOutOfMemoryError -XX  UseConcMarkSweepGC -XX  UseParNewGC -XX SurvivorRatio 8 -XX  UseCompressedOops -Dcom sun management jmxremote port 8181 -Dcom sun management jmxremote authenticate false -Dcom sun management jmxremote ssl false  JAVA OPTS   JAVA OPTS -Dserver name  HOSTNAME

User · Answer

Take care with change in Debian distributions  I tried to change CATALINA OPTS in my Debian 7 and the results where that tomcat didn t start anymore  Thus I solved this issue by changing the property JAVA OPTS in place of CATALINA OPTS  like this  export JAVA OPTS  -Xms512M -Xmx1024M

User · Answer

setenv sh is better  because you can easily port such configuration from one machine to another  or from one Tomcat version to another  catalina sh changes from one version of Tomcat to another  But you can keep your setenv sh unchanged with any version of Tomcat   Another advantage is  that it is easier to track the history of your changes if you add it to your backup or versioning system  If you look how you setenv sh changes along the history  you will see only your own changes  Whereas if you use catalina sh  you will always see not only your changes  but also changes that came with each newer version of the Tomcat

User · Answer

You must not use    Simply use this   export CATALINA OPTS  -Xms512M -Xmx1024M

User · Answer

After spending good time time on this   I found this is the what the setenv bat must look like   No   characters are accepted in batch file    set CATALINA OPTS -Xms512m -Xmx1024m -XX PermSize 128m -XX MaxPermSize 768m  echo hello   CATALINA OPTS

User · Answer

Just came across this and I ve implemented Nathan s solution   add the line  changing the values as required    export JAVA OPTS  -Xms512M -Xmx1024M    to  usr share tomcat7 bin setenv sh  If that file doesn t exists then create it and  chown root root it chmod 755 it   And then restart tomcat and  check it with  ps aux   grep logging   Which should just pick up the instance and show the java parms

User · Answer

Use following command to increase java heap size for tomcat7  linux distributions  correctly   echo  export CATALINA OPTS  -Xms512M -Xmx1024M    gt   usr share tomcat7 bin setenv sh

User · Answer

If it s not work in your centos 7 machine  export CATALINA OPTS  -Xms512M -Xmx1024M   then you can change heap memory from  vi  etc systemd system tomcat service file then this value shown in your tomcat by help of ps -ef grep tomcat

[java] Tomcat 7: How to set initial heap size correctly?

Examples related to java

Examples related to linux

Examples related to tomcat7

Examples related to heap-memory