> > I have had this problem to with connection pooling. And i found that i > did'nt want to have 100 of possible connections as maxActive... > So i craete the SingleConnectionProvider provider - On connection for each > system.
> If you want to have a little better performance you should use the > SinglePerThreadConnection provider. > This connection provider creates on > connection for each running tomcat thread. So the number of SinglePerThreadConnections depends on how many concurrent requests you have going to the dbforms servlet -- correct or not? > This are connections you ever > need because each thread handles only request at a given time. And because > each connection can handle more then one statement and resultset this works > perfect. > > Oh by the way, the SingleConnection providers do exactly this. Create a > connection - held this connection open fore ever and only closes the > unneeded statements and resultset during connection close. -- Shawn <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
