How about Tomcat 6.0?Had the memory leaks been fixed in Tomcat6.0?
Mark Thomas-15 wrote:
Tomcat 5.0.x has some memory leaks but as far as I recall they were
mostly related to context reload.
If you are reloading your app, I'd suggst an upgrade to the latest
5.5.x. If you are not
Dear Mark:
How about Tomcat 6.0?The lastest version is 6.0.x.Had the memory leaks been
fixed in Tomcat6.0?
Mark Thomas-15 wrote:
Tomcat 5.0.x has some memory leaks but as far as I recall they were
mostly related to context reload.
If you are reloading your app, I'd suggst an upgrade to
You configured your JVM to use 1GB of memory plus 800MB for perm space.
This only makes sense, if your machine has that much memory. As far as I
know, perm adds to the heap. You system has 4 GB of memory. Are there
other big memory consumers there? Can you check the size of the process?
Dear Rainer
The memory properties are below.
xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx
Physical Memory: 4097.7 MBxx x
xx xxReal Memory: xx
x
xx xx Active:
I have been using Tomcat 6.0 since it was released and I would say that it
is much better
that Tomcat 5.x. As addressed in its release document, besides support
Servlet 2.5 and
JSP2.1, Tomcat 6.0 made following improvements upon Tomcat 5.5:
- Memory usage optimizations
- Advanced IO
I am a Chinese and English is not well,but I will try my best to express
myself.I have HP-UX operation system with JDK1.5 and sybase.But after tomcat5.0
running for some times ,it would out of memory.The tomcat5.0 process
continuously allocated swap space but not released it.So when swap
Tomcat 5.0.x has some memory leaks but as far as I recall they were
mostly related to context reload.
If you are reloading your app, I'd suggst an upgrade to the latest
5.5.x. If you are not reloading, then your app probably has a memory
leak. I'd suggest using a profiler such as YourKit to try
Tomcat 5.0.x has some memory leaks but as far as I recall they were
mostly related to context reload.
If you are reloading your app, I'd suggst an upgrade to the latest
5.5.x. If you are not reloading, then your app probably has a memory
leak. I'd suggest using a profiler such as YourKit to try
