I have a weird issue on a server. The server is a Windows 2000 Server with IIS installed and Tomcat 4.1.12. It uses the isapi connector to proxy requests from IIS to Tomcat. Everything has been working fine with this setup for several months. Last week, I tried to add a new application to the Tomcat instance. This application is a bit more than the existing app - it has a JDBCRealm and connection pool setup.
Here's the strange behavior. After starting Tomcat, the memory used climbs to about 48MB, but when I hit the first page in the new app - the memory usage by "java.exe" starts climbing off the charts. It increases by about 1 MB every second and before long it reaches the threshold (256MB) and it throws an out of memory error - and it's just on the welcome page! The only thing I've changed since dropping my app in tomcat is to use tomcat's authentication, rather than passing it through from IIS. Has anyone else seen this behavior? Thanks, Matt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
