I'm getting complaints from my host about excessive CPU usage in my web app. I'm unable to use connection pooling in the servers environment so I'm using a new connection for each DB call (and there are quite a few). The connections are promptly closed afterwards. Is it a better idea to use a connection for each session and check to see if its still valid each time it is needed? There are many lookup lists maintained in sessions as ArrayLists. Should those be made application-level? I also have a number of static factory classes that perform database/business logic. Should those be made into Singletons? What is a good monitoring tool for development on Win2000? The server is Linux but I have no way of seeing how big the load is....any help would be greatly appreciated.
Thanks, Bill -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
