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?

Do not edit catalina.sh. Please see the proper way of doing this described in this post: [http://stackoverflow.com/a/10950387/926057](http://stackoverflow.com/a/10950387/926057) — oᴉɹǝɥɔ, Jun 08 '12 at 14:22

score 114 · Accepted Answer · answered Aug 01 '11 at 11:03

114

You must not use =. Simply use this:

export CATALINA_OPTS="-Xms512M -Xmx1024M"

answered Aug 01 '11 at 11:03

Joachim Sauer

302,674
57
556
614

3

I created a file setenv.sh in the tomcat bin folder and added this line, and it worked! – Babu James Jan 26 '16 at 17:10

score 27 · Answer 2 · answered Dec 16 '14 at 13:03

27

Use following command to increase java heap size for tomcat7 (linux distributions) correctly:

echo 'export CATALINA_OPTS="-Xms512M -Xmx1024M"' > /usr/share/tomcat7/bin/setenv.sh

answered Dec 16 '14 at 13:03

MeJ

1,088
10
18

If in Debian I do recommend I do recommend changing `/etc/default/tomcat7` instead, rather than creating the setenv.sh file in the equivalent location. Is is a far less obscure location. – Rui F Ribeiro Nov 08 '16 at 07:35

score 11 · Answer 3 · answered Nov 25 '13 at 03:46

11

You might no need to having export, just add this line in catalina.sh :

CATALINA_OPTS="-Xms512M -Xmx1024M"

answered Nov 25 '13 at 03:46

Phat H. VU

2,350
1
21
30

23

**NOT** to catalina.sh! Put it inside `/usr/share/tomcat7/bin/setenv.sh`, that's the right place for it. – kazy Jan 21 '15 at 11:42

score 3 · Answer 4 · answered Feb 01 '15 at 00:59

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.

score 3 · Answer 5 · answered May 20 '16 at 20:14

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/

score 2 · Answer 6 · answered Jan 28 '17 at 07:45

2

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%"

answered Jan 28 '17 at 07:45

Dinesh Rajendran

21
1

score 1 · Answer 7 · edited May 20 '15 at 02:59

1

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"

edited May 20 '15 at 02:59

Nathan Walters

4,116
4
23
37

answered May 20 '15 at 02:29

Roberto C. Rodriguez-Hidalgo

607
9
18

score 1 · Answer 8 · edited Jan 21 '16 at 12:21

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

mdev · Answer 9 · 2016-08-24T23:42:06.290

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"

score 0 · Answer 10 · answered May 20 '19 at 06:17

0

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.

answered May 20 '19 at 06:17

Birendra Rawat

1,307
1
8
8

Tomcat 7: How to set initial heap size correctly?

10 Answers10

Linked