Hi, You could set this very high if you wanted too. Typically there's a bottleneck along the way, such as a database that can only handle a limited number of connections, and your app not being the only user of said database. But if you're the database's only user, and it's on a huge machine that can handle a virtually unlimited number of concurrent connections, have a blast ;)
Yoav Shapira http://www.yoavshapira.com >-----Original Message----- >From: Stephen Charles Huey [mailto:[EMAIL PROTECTED] >Sent: Monday, December 13, 2004 3:51 PM >To: Tomcat User >Subject: maxActive in server.xml's ResourceParams > >In Tomcat 4's server.xml, one of the ResourceParams elements is >maxActive (set to 20 by default). I'm wondering if there's any reason >why I wouldn't set this very high if I have a virtually unlimited number >of users for our Oracle database...I'm not sure how much this applies to >us since I don't believe we're using built-in connection pooling (we're >using some slightly customized classes--nothing nonstandard, though). >Anyway, thanks for any tips... > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
