Greetings all,
I would like someone to shed a bit of light on when exactly Tomcat throws an
OutOfMemory exception. Is it when its physical memory usage (working set)
reaches the maximum limit configured in the JVM startup parameters, or are
other conditions that can cause this? I've noticed
hi,
there are many occasions.
1. if there is no memory left (-Xmx)
2. if there is no perm gen space left (for example to many jsps)
3. if there is not enough space in the current heap and no time to
enlarge the heap (xms xmx)
4. if a new thread couldn't be created
5-10 whatever the jvm vendor
Thanks for the clarification. The JVM doesn't indicate which of these
conditions actually caused the exception, though, does it?
-Original Message-
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 30, 2008 3:55 PM
To: Tomcat Users List
Subject: Re: When does Tomcat
Caldarale, Charles R wrote:
From: André Warnier [mailto:[EMAIL PROTECTED]
Subject: Re: Manager app language
Personally, I don't see anything in there that looks like it
is setting the global JVM user.language property.
So what was the basis of your previous statement that the JSP is doing
Hi.
I am monitoring a Tomcat during startup, using jconsole.
This Tomcat's JVM is started with the switches -Xms200M -Xmx200M, and
it starts a rather heavy webapp that just about occupies Tomcat 100%
during 5 minutes whenever I start it. (*)
In the memory tab of jconsole, I observe that one
From: Karim Zaki [mailto:[EMAIL PROTECTED]
Subject: RE: When does Tomcat throw an OutOfMemory exception?
The JVM doesn't indicate which of these conditions
actually caused the exception, though, does it?
Depends on the JVM version and vendor. Newer ones from Sun are much better at
From: André Warnier [mailto:[EMAIL PROTECTED]
Subject: Memory pool Survivor space
This Tomcat's JVM is started with the switches -Xms200M
-Xmx200M
That's rather small for these days; I presume this is the toy machine you use
to test with.
In the memory tab of jconsole, I observe that one
Dear Chuck,
To add to Leon's list: running out of file descriptors.
Actually, in such situations you get 'java.io.IOException: Too many
open files' or 'java.net.SocketException: Too many open files'. Not an
OutOfMemory error.
/nitpick
--
Kees Jan
http://java-monitor.com/forum/
[EMAIL
From: Kees Jan Koster [mailto:[EMAIL PROTECTED]
Subject: Re: When does Tomcat throw an OutOfMemory exception?
Actually, in such situations you get 'java.io.IOException: Too many
open files' or 'java.net.SocketException: Too many open files'. Not an
OutOfMemory error.
Only if it's related to
Dear Chuck,
Actually, in such situations you get 'java.io.IOException: Too many
open files' or 'java.net.SocketException: Too many open files'. Not
an
OutOfMemory error.
Only if it's related to an application-initiated action, such as
opening a stream. If FD exhaustion is detected
10 matches
Mail list logo