Rick Fincher wrote:
The javac in J2SE 1.4 has the memory leak 1.1.1 works OK under Solaris.
- Original Message -
From: Ralph Einfeldt [EMAIL PROTECTED]
- First make shure that you don't have memory leaks on your own.
- Make shure that you store as few data in sessions as possible.
Remember that the sessions stay around for 30 minutes after the
last action in the action. (30 minutes is the default for the
session timeout). This way the number of concurrent sessions
can be much higher than the number of active sessions. If you
get 1 user per minute and each stays for one minute you will have
30 concurrent session, but only 1 active session.
- The only memory leak that I know in this environment is the java
compiler of the JDK. It has been reported that in some versions
of the JDK javac has a memory leak. So each time tomcat compiles
a page you will lose some memory.
There are two solutions to this problem:
- Use only precompiled JSP's (jspc)
- Use another compiler (jikes) (Don't know if it's available
for solaris)
- I have read that some VM versions have trouble to invoke the gc
if there isn't any available memory. It was suggested to issue
a System.gc() if your free memory is below a watermark.
I didn't investigate this further.
- Use OptimizeIT to find out where the leaks are.
-Ursprüngliche Nachricht-
Von: David Hladky [mailto:[EMAIL PROTECTED]]
snip/
Could someone with experience tuning Solaris JVMs
give me and my friends a hint or two on how to force the JVM to
garbage
collect/tune. Or is this just a memory leak in Tomcat and or JBOSS?
snip/
Thanks for the hints, We've torn our code apart with OptimizeIt and found out that it
really isn't the problem. I think you are on to something about the jsp precompiled
thing though. Thanks again. I'll try a few of the other things you've mentioned.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
