It's possible that you are out of file descriptors.
Find and use 'lsof' (ls open files) running it against that process.
I've seen Java report OOM when it can not allocate a file because
a File is nothing more than another object associated with the resource.
If this is the case you will have to
Quoting Shannon Scott [EMAIL PROTECTED]:
Greetings,
Tomcat is running, and was working fine until the memory usage went up
to 167, now none of the .jsp pages will respond ( the server hangs
forever ).
The last entries from the Catalina.out are :
java.lang.OutOfMemoryError
Well it could be because -Xmx256M means absolutely nothing to the VM. You
need to use -Xmx256m. Notice the case of the m. It is *very* important.
Not according to the docs:
-Xmxn
Specify the maximum size, in bytes, of the memory allocation pool.
This value must a multiple of 1024
Quoting Dale Lum [EMAIL PROTECTED]:
Well it could be because -Xmx256M means absolutely nothing to the VM.
You
need to use -Xmx256m. Notice the case of the m. It is *very*
important.
Not according to the docs:
Ahh... Then I eat my words. Sorry about that. I don't know why I
On Thu, Sep 23, 2004 at 12:14:24PM -0500, Jacob Kjome wrote:
: Ahh... Then I eat my words. Sorry about that. I don't know why I remembered
: the case as being important?
Depends on the vendor/version of the JDK... just as some care about the
space or equals-sign between the flag and its arg.
To: Tomcat Users List
Subject: Re: Tomcat dies at 167M
Quoting Shannon Scott [EMAIL PROTECTED]:
Greetings,
Tomcat is running, and was working fine until the memory usage went up
to 167, now none of the .jsp pages will respond ( the server hangs
forever ). The last entries from
, September 23, 2004 11:35 AM
To: Tomcat Users List
Subject: Re: Tomcat dies at 167M
Quoting Shannon Scott [EMAIL PROTECTED]:
Greetings,
Tomcat is running, and was working fine until the memory usage went up
to 167, now none of the .jsp pages will respond ( the server hangs
forever
