Re: JDBC Connection question
Which server do you use? Weblogic, Websphere, ... support connection pooling. (Caroline Jen) Oracle 9iAS Supports DataSources with pooling as well. (Wade Chandler) Thats not the issue. Whatever server i use, i'll have to deploy the application somewhere. My company does not have any servers, so we have to use an outside server. Won't the need to configure server.xml (or something similar) give me any troubles? Why isn't it possible to configure connection pooling through web.xml? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDBC Connection question
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]
Re: JDBC Connection question
Which server do you use? Weblogic, Websphere, ... support connection pooling. --- Carlos Pereira [EMAIL PROTECTED] wrote: 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] __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JDBC Connection question
Oracle 9iAS Supports DataSources with pooling as well. Wade -Original Message- From: Caroline Jen [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2003 2:25 PM To: Tomcat Users List Subject: Re: JDBC Connection question Which server do you use? Weblogic, Websphere, ... support connection pooling. --- Carlos Pereira [EMAIL PROTECTED] wrote: 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] __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDBC Connection question
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 --- Carlos Pereira [EMAIL PROTECTED] wrote: Hi list, my application currently uses ONE connection object to communicate with the database. The connection is set with an initializer servlet (load_on_stratup=0), and all users use that connection to retrieve data. Is this the best approach, or should i create a connection per user? Why? Where can i know more? The security system works on top of the database, so that's not a problem. I'm more concerned with performance and concurrency. Regards and thanks, Carlos Pereira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JDBC Connection question
You can only run one transaction per connection. So if you depend on rollbacks or things of this nature this will become an issue. Also, your DBMS may support a limited number of threads per connection. You should find this out. Also, if you disconnect and reconnect from one thread and another is performing work, or threads change some non-protected(non thread safe) variables, then you'll have issues. Wade -Original Message- From: Carlos Pereira [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 12:46 PM To: Tomcat Users List Subject: JDBC Connection question Hi list, my application currently uses ONE connection object to communicate with the database. The connection is set with an initializer servlet (load_on_stratup=0), and all users use that connection to retrieve data. Is this the best approach, or should i create a connection per user? Why? Where can i know more? The security system works on top of the database, so that's not a problem. I'm more concerned with performance and concurrency. Regards and thanks, Carlos Pereira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JDBC Connection question
Best to use a connection pool. Look at the Data Sources in Tomcat. Wade -Original Message- From: Carlos Pereira [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 12:46 PM To: Tomcat Users List Subject: JDBC Connection question Hi list, my application currently uses ONE connection object to communicate with the database. The connection is set with an initializer servlet (load_on_stratup=0), and all users use that connection to retrieve data. Is this the best approach, or should i create a connection per user? Why? Where can i know more? The security system works on top of the database, so that's not a problem. I'm more concerned with performance and concurrency. Regards and thanks, Carlos Pereira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
