I was under the impression that if you used the "sql:dataSource" tag that you were essentially using whatever connection mgmt was behind the data source. Therefore, you would need to consult how you configured the Data Source in Tomcat to get connection pooling.
Reading further maybe you have already done this? Anyway, I here is the URL for setting up Tomcat data sources. http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-how to.html Also, you may want to check the JSTL spec -- it has a fair amount of info on accessing data sources. Bill Siggelkow [EMAIL PROTECTED] -----Original Message----- From: Roy Benjamin [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 5:12 PM To: Tag Libraries Users List Subject: Tomcat JNDI JDBC connection/JSTL DataSource I think I'm having some trouble with JDBC access via JSTL. I'm uncertain, but performance seems very sporadic and may relate to connection overhead and resource exhaustion. Now, I only see one form for the sql:dataSource tag and it seems not to allow for any connection management or tuning. What I am wondering is if there is a resouce usage efficiency issue with jstl sql access. Prior to using jstl I usd the JNDI lookup for a JDBC resource that was actually pooled and managed by Tomcat for that context. (I think this is more or less correct notion.) Anyway, supposing I set up the same JNDI resource for an app that uses jstl/sql ? Can I create a jstl/sql dataSource thatreally uses the pooled resources managed by Tomcat? Are the reasons why this is a good idea? Is it possible? Thanks Roy --------------------------------------------------------------------- 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]
