Hi George Your remark is almost correct. What I did is that I store the result of the resultset (which can go up to million lines of rows) in a batch of Java beans. Then I set the beans to the HTTP Request and pass them to the receiving JSP.
But I do remember to return the connection to the pool. I also try to kill the statements, result sets, etc by setting them to null. But I realize that java might wait for the memory to be cleared by the garbage collector. This goes back to my second problem. If the user closes the browser, the request object form the servlet would lost its way to return the result. And this will hog the tomcat performance for a while. Any tips would greatly be appreciated. TIA Rendra -----Original Message----- From: George Sexton [mailto:geor...@mhsoftware.com] Sent: Thursday, April 08, 2010 11:42 PM To: 'Tomcat Users List' Subject: RE: Tomcat scalability setting - need help please > -----Original Message----- > From: Pid [mailto:p...@pidster.com] > Sent: Thursday, April 08, 2010 8:49 AM > To: Tomcat Users List > Subject: Re: Tomcat scalability setting - need help please > > When you run the query in your application how are you doing it, e.g. > by > calling a stored procedure, or by executing exactly the same SQL > statement? > Most likely the application is storing result sets on the session. George Sexton MH Software, Inc. 303 438-9585 www.mhsoftware.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
