when you say SAP, I take it is refering to SAPDB. The first thing you to do is to time how long it takes to execute the query. If the query is not a problem, then I would move on to timing the processing time in struts. What I've done in the past is to take some of the production queries and run them against the database for increasing loads. typically I will do increasing number of concurrent queries and increasing dataset. generally, if your queries are taking more than a couple of seconds, it will be your bottleneck. assuming the db isn't the problem, I would time the jsp by getting the time at the top and at the bottom. normally no response is the cause of the database and not Tomcat. peter
[EMAIL PROTECTED] wrote: When I say "it doesn't respond very well" I refer that when there are most people entering to the application sometimes when you type a action on the navigation bar on the browser it doesn't respond anything, it doesn't show the page, appear error 404 not found, and if you wait a moment and try after it responds well. Our application is written with struts and obligatory use jsp tag libs, our application use connection pool and access to Sap continously, that application show data extracted online from Sap. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------- Do you Yahoo!? Free Pop-Up Blocker - Get it now
