> You can only run one transaction per connection. > Also, your DBMS may support a limited number of threads per connection. (Wade Chandler) Ok. So, using one connection for the whole application is out of question. My other alternatives are connection pooling and using one connection per user.
The server is supposed to have between 300/1000 people online at a time. I'm sure my question is very basic, but i want to know: what does it mean to have 1000 concurrent connections to the database (lets forget the dbms connection limit, just performance)? > Please use a connection pool. For Instruction: > http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html > and http://www.mysql.com/articles/connection_pooling_with_connectorj.html (Caroline Jen) I read it all. Connection pooling looks like the solution for all my problems. But, i had to configure server.xml to put it working. What about when i have to deploy the application? And if the server is NOT Tomcat, will it support connection pooling? Best regards, Carlos Pereira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
