JSP Intranet application Crashes tomcat after 5 hours of continuous running.
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Rony_Zacharia
Posted On:   Wednesday, October 3, 2001 07:14 PM

We developed an Intranet Application for approx 50 users. Plat form - WinNT, Apache, tomcat, Poolman, SQL Server and JDBC-ODBC Bridge driver. Nearly 1500 JSP Pages, 250 Bean files and 300 Database Tables. Most of the screens contain big text area which capturing large amount of data. In production site, the application is running fast for an hour then gradually slowing and nearly after 7 hours the server response become dead slow. At that time the CPU Usage is in 100% always. JVM is consuming 99% of CPU time but SQL Server is occupying too much memory space. Finally the tomcat service is getting stopped. Aybody have any idea on this? We are using poolman software for connection pooling and JDBC-ODBC Bridge driver for connectivity.    More>>

We developed an Intranet Application for approx 50 users.
Plat form - WinNT, Apache, tomcat, Poolman, SQL Server and JDBC-ODBC Bridge driver.
Nearly 1500 JSP Pages, 250 Bean files and 300 Database Tables. Most of the screens contain big text area which capturing large amount of data.
In production site, the application is running fast for an hour then gradually slowing and nearly after 7 hours the server response become dead slow. At that time the CPU Usage is in 100% always. JVM is consuming 99% of CPU time but SQL Server is occupying too much memory space. Finally the tomcat service is getting stopped.
Aybody have any idea on this? We are using poolman software for connection pooling and JDBC-ODBC Bridge driver for connectivity.
Rony

   <<Less

Re: JSP Intranet application Crashes tomcat after 5 hours of continuous running.

Posted By:   Alex_Chaffee  
Posted On:   Friday, October 26, 2001 09:11 AM

Sounds like there's a memory leak. Likely in your database driver -- the JDBC-ODBC Bridge is not recommended for production use.
About | Sitemap | Contact