Also the server doesn't break if I start it as an application and not as a sevice?Though it just seems to increase in memory slowly but doesn't run out of memory. I tried running a simple load test with 3 users. Again after researching could using log4j and logging be an issue? I am using jdk1.4.0_04 and tomcat 5.0.28 . I used jdk1.4.0_04 because on the sun bug databse they said 1.4.1_02 had a bug related to Stringbuffers usage.(since I see char[] array increasing in JProbe memory debugger every time I refresh the page!!) but that didn't help either.
Also I was reading about classloader issues and it really seems like a reference is not released for objects created which ultimately fills up memory. http://opensource2.atlassian.com/confluence/spring/pages/viewpage.action?pageId=2669 In my case I think this could be an issue? Any JDBC driver loaded in the application (from the WEB-INF/lib directory) will be registered in the system-wide DriverManager. Thanks |---------+----------------------------> | | Gary Evesson | | | <[EMAIL PROTECTED]| | | m> | | | | | | 03/07/2006 01:01 | | | PM | | | Please respond to| | | "Tomcat Users | | | List" | |---------+----------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: Tomcat Users List <users@tomcat.apache.org> | | cc: | | Subject: Re: Tomcat 5.0.28 memory leak | >------------------------------------------------------------------------------------------------------------------------------| [EMAIL PROTECTED] wrote: > Yes I am putting it out in the session but I get the error after the > service has broken and at that point its probably trying to persist data??? > and that should be serializable. > My issue is why doesthe service break in the first place? > I am just doing refesh on a page several times?? > The breakage of the service is not indicated in the exception that you have sent. This is the container attempting to persist the sessions as the web app is shutting down. Assuming the class you are adding to the session is simple, then the standard serialization will work fine. Just make your class implement Serializable. You need to investigate further. > I was reading this could this be an issue? > http://issues.apache.org/bugzilla/show_bug.cgi?id=36541 > Unlikely. The exception is not related to that. Concurrency issues such as this would require significant load from one user. I assume that you are not generating high load? - Gary --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
