Hi J=FCrgen,
Thanks for the info.
Honestly, I don't know whether it's due to memory outage. But something is=
=20
happening during the shutdown process. As you can see in the JAVA_OPTS=20
setting, I have set the max heap size to 1G which is 50% of the total ph
ysical memory and, if I'm not mistaken, I think we are running only one=20
application in the tomcat so I don't think it's memory related but still=20
not sure. The weird thing is instead that only the tomcat is supposed to=20
crash, the whole server does. If I set the AgressiveHeap option is there=20
still a possibility to eat up all the availble memory even if I set the=20
max heap size=3F
Best regards,
Adrian
J=FCrgen Link <juergen.link@googlemail.com>=20
11/18/2011 02:59 PM
Please respond to
"Tomcat Users List" <users@tomcat.apache.org>
To
"Tomcat Users List" <users@tomcat.apache.org>
cc
Subject
Re: Tomcat Causes Server to go Panic/Crash
Hi Adrian,
you might want to replace the AggressiceHeap option by a decent initial
heap size, e.g. Xms=3D64m.
AggressiveHeap seems to eat up all available memory:
[...] The size of the initial heap is calculated based on the size of the
physical memory and attempts to make maximal use of the physical memory=20
=66or
the heap (i.e., the algorithms attempt to use heaps nearly as large as the
total physical memory). (see
http://java.sun.com/docs/hotspot/gc1.4.2/#4.2.2.%20AggressiveHeap%7Coutline
)
Did you investigate the cause of server panic (e.g. crash dump)=3F Is it
memory related=3F
Cheers
J=FCrgen
2011/11/18 Adrian Zara <adrian.zara@aonhewitt.com>
> Hi Chuck,
>
> Thanks for the prompt reply. Please refer to the following requested=20
info:
>
> Tomcat version: Tomcat: 5.5.31
> JVM version: gij (GNU libgcj) version 3.4.2 20041017 (Red Hat=20
3.4.2-6.fc3)
>
> If the JAVA_OPTS affects the shutdown process, then I have to find out
> what is the best setting for this env variable since I often encounter=20
the
> server panic during shutdown. What do you think=3F Both env variables (
> JAVA_OPTS and CATALINA_OPTS) are used throughout the catalina.sh file so=
=20
I
> cannot remove one and retain the other. Previously, JAVA_OPTS is set to
> '-Xmx512m -XX:+AggressiveHeap' so I thought increasing the heap size to
> 1024 will resolve the server panic. I have two tomcat seated on two
> different machines. When I increased the JVM heap size on the first
> machine and tried to restart a couple of times, I didn't encounter any
> server panic. But when I tried on the other machine, even on the first
> attempt, the server goes to panic. The two machines has the same specs.
> Both tomcats contain the same web application.
>
> Do you think it is really the tomcat settings that causes the server to
> panic=3F Should I consider using -server mode in the JAVA_OPTS=3F
>
> Best regards,
> Adrian
>
>
>
>
> "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>
>
> 11/18/2011 01:46 PM
> Please respond to
> "Tomcat Users List" <users@tomcat.apache.org>
>
>
>
> To
> "Tomcat Users List" <users@tomcat.apache.org>
> cc
>
> Subject
> RE: Tomcat Causes Server to go Panic/Crash
>
>
>
>
>
>
> > From: Adrian Zara [mailto:adrian.zara@aonhewitt.com]
> > Subject: Tomcat Causes Server to go Panic/Crash
>
> > Tomcat Version: 5.5.x
>
> Exact Tomcat version=3F There have been at least 15 releases of 5.5.
>
> > JAVA_OPTS=3D'-Xmx1024m -XX:+AggressiveHeap'
>
> Note that setting JAVA_OPTS affects all Tomcat Java executions,=20
including
> the shutdown process. You should be using CATALINA_OPTS, not JAVA_OPTS.
>
> > settings in the catalina.sh
>
> You should be creating a setenv.sh script to hold environment variable
> settings, not modifying catalina.sh.
>
> > Server info: Redhat 3.9.2-6.fc3
> > CPU: 3.4 GHz
> > Memory: 2GB
>
> Exact JVM version=3F
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
>
>
> The information contained in this e-mail and any accompanying documents
> may contain information that is confidential or otherwise protected from
> disclosure. If you are not the intended recipient of this message, or if
> this message has been addressed to you in error, please immediately=20
alert
> the sender by reply e-mail and then delete this message, including any
> attachments. Any dissemination, distribution or other use of the=20
contents
> of this message by anyone other than the intended recipient is strictly
> prohibited. All messages sent to and from this e-mail address may be
> monitored as permitted by applicable law and regulations to ensure
> compliance with our internal policies and to protect our business.=20
E-mails
> are not secure and cannot be guaranteed to be error free as they can be
> intercepted, amended, lost or destroyed, or contain viruses. You are=20
deemed
> to have accepted these risks if you communicate with us by e-mail.
>
>
>
The information contained in this e-mail and any accompanying documents may=
=
contain information that is confidential or otherwise protected from =
disclosure. If you are not the intended recipient of this message, or if =
this message has been addressed to you in error, please immediately alert =
the sender by reply e-mail and then delete this message, including any =
attachments. Any dissemination, distribution or other use of the contents o=
=66=
this message by anyone other than the intended recipient is strictly =
prohibited. All messages sent to and from this e-mail address may be =
monitored as permitted by applicable law and regulations to ensure =
compliance with our internal policies and to protect our business. E-mails =
are not secure and cannot be guaranteed to be error free as they can be =
intercepted, amended, lost or destroyed, or contain viruses. You are deemed=
=
to have accepted these risks if you communicate with us by e-mail.=20
|