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]
