What is Tomcat's limitation on multiple connection to database?
Tomcat has no limit on DB connections. Unless you are using a Realm, Tomcat does not have any control over db connections.
I have a simple servlet application that connects to Oracle database for data. Since it is a very simple application, no connection pooling is used. Someone raised a question on whether Tomcat can handle hundreds of calls to the servlets and hundreds of connections to the Oracle database.
Again, Tomcat doesn't care. The VM may care, though. Especially with Oracle, JDBC connections take a long time to establish and use of a lot of memory on the server, and often the client. You should use connection pooling for a number of reasons:
1. Performance (re-using connections takes less time than creating more)
2. Resource limiting (pool limits the number of total connections)
3. Configuration (easier to manage a connection pool than code to create connections on the fly and make sure they are closed/managed appropriately)
-chris
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
