Ralph Einfeldt wrote: > - The memory that a vm uses is never decreasing (At least I don't > know any that behave that way) > To understand that you have to see two different things: > - the memory that is used by the vm > - the memory inside the vm > All vm's that I know, don't return memory to the os. What > happens during a gc is just that inside the vm the memory is > marked as free. So the only save indicators for the question > 'how many memory is currently in use' are the methods > java.lang.Runtime.get*Memory. > - To a certain degree it is normal that the memory is increasing. > Reasons for that: > - each session needs some memory, that is only released after > the session has timed out. If you create sessions very fast > this can consume quite some memory. (If you are creating > the sessions faster as they dye tomcat will die with an out > of memory error.)
To avoid that, you can either: - use some more scalable manager (JDBC store or similar) - set a maximum amount of active sessions (session creation will be denied after that until some timeout) Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
