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 during
> 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
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.
--
Kees Jan
http://java-monitor.com/forum/
[EMAIL PROTECTED]
> 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 Su
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 T
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 t
