Hello,
During stress testing of our application the Tomcat java.exe process keeps growing in both memory size and number of threads used. Our test is basically to repeatedly log in to our authentication servlet. We are using the same login over and over. I added logic to track the previous HttpSession object and invalidate it every time the same user logs in with a new session. This did not fix the memory problem. The servlet being tested only allocates local variables which should be cleaned up after a given request completes. Are there some configurations I need to add or check? Any ideas as to why the Tomcat process would keep growing? Is there something I need to do to ensure garbage collection is run properly? Any help would be appreciated. We are running Tomcat 3.2.3 with the isapi redirector with IIS on Windows 2000. Thanks, Keith
