> From: opensta [mailto:[EMAIL PROTECTED]
> Subject: Re: Tomcat 4.1.24 - Out of memory
>
> just increase your max memory of JVM ,
> problem will get solved
That's called attacking the symptom, not the problem - a rather
short-sighted approach that might postpone the issue t
opensta wrote:
> just increase your max memory of JVM ,
> problem will get solved
If the problem is a memory leak this suggestion will not work. It will
reduce the frequency of the OOM errors (since it will take longer for
the leak to fill all the available memory) but it will not fix the root
cau
just increase your max memory of JVM ,
problem will get solved
--
View this message in context:
http://www.nabble.com/Tomcat-4.1.24---Out-of-memory-t1509167.html#a4098698
Sent from the Tomcat - User forum at Nabble.com.
-
To un
Kingston Sew wrote:
> Any ideas on what is the cause of the problem?
Sounds like your application has a memory leak. A profiler tool should
be able to show you where.
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additio
1. some jsps or servlets have probably forgotten to close some Statement or
ResultSet or Connections. Fix them.
2. You could try using connection pooling if possible.
3. remove any unwanted jars from your tomcat.
-
Manivannan Palanichamy
http://geocities.com/manivannan57
--
View this message
First guess, there are many memory leaks in your application...things
like unclosed connections and all... Did you check on those?
--
Vivek.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PRO