I've seen it, but couldn't make it working.
Anyway I sorted out the leak memory problem using the Netbeans Profiler
which is actually quite nice.
Thanks for help!
Tomek
Glauco Pimentel Gomes wrote:
In Eclipse you could use the "Eclipse Test & Performance Tools
Platform Project" [1] to profile.
[1] http://www.eclipse.org/tptp/
Glauco P. Gomes
Tomek Szpinda escreveu:
Thorbjørn Ravn Andersen wrote:
Tomek Szpinda skrev den 11-05-2007 16:35:
java.lang.OutOfMemoryError: Java heap space
It looks to me(probably I'm wrong:)) that Tomcat doesn't release
memory after session.invalidate()?
You need to ensure yourself that your objects can be garbage
collected by removing all the reference you have to them.
If any one can give me some hints I'd be thankful.
Best Regards,
at java.lang.StringBuffer.append(StringBuffer.java:320)
at org.apache.log4j.NDC$DiagnosticContext.<init>(NDC.java:426)
at org.apache.log4j.NDC.push(NDC.java:350)
at com.ylem.knowledge.logger.Log.add(Log.java:18)
A guess could be that this module does not properly release its
log4j NDC-objects after use.
This might be a good time to learn and use the profiler i.e. in
Netbeans.
I tried to find something for eclipse, but that's not so easy...
Eclipse Test and Performance Tools Platform
<http://www.eclipse.org/tptp/>
So first need to learn Netbeans... ;) but learning is never bad
thing, so better I'll start now.
Thanks,
Tomek
