-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Which kernel are you running? If you are running 2.4 I could imagine
that it could be an out of process/ thread limit.
Java used to report - out of memory - even for out of processes/
threads problems
I think 2.4 had a default limit of 256 Process/ threads.
ulimit -a will show you how high your process limits are set.
Regards
Andrew
On 15/11/2006, at 11:14 AM, Santosh Puranshettiwar wrote:
Gaurav Kushwaha wrote:
A quick fix would be to specify minimum and maximum heap size
using JVM
parameters -Xms and -Xmx. -Xms specifies the minimum heap size and
-Xmx is
used to determine the maximum allowed heap size.
So, lets say if you have enough memory to allocate 512 MB to your
java
process you shoud write something like:
java -Xms512M -Xmx512M.
Well in most cases the default heap size does good enough. In some
cases we may have to increase it. But in case this too doesn't
work, try profiling your code.
On 11/14/06, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Subject: Tomcat Out Of Memory
>
> We are running Tomcat 4.1.18 on RedHat ES3 using JDK 1.4.2_02.
> What is causing the error message below and What can I do to
solve it?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFFWworW126qUNSzvURAqsyAJ4hFkVoVk5fVL9Pxl6K97cRcs1yZwCfbz+N
Uz3mssqyZM/75TSvVqU7Uak=
=75sK
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
