Hello. I've installed and tested successfully an example of JDBC access using the Tomcat's connection pooling (JNDI + Datasource), showed at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html.However, I've some doubts... I'd like to know if in Tomcat's connection pooling I can increase the number of connections if it hasn't anyone available. You know that in my server.xml I set three important parameters: # maxActive - The maximum number of active instances that can be allocated from this pool at the same time. # maxIdle - The maximum number of connections that can sit idle in this pool at the same time. # maxWait - The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception. When I've seen the parameter maxWait, I've understood that the Tomcat's Connection Pooling doesn't create more connections if there are no more available. Is that true or not? Thanks in advance.
===== ____________________________________________________________ Cristiano Moreira Silva Site - http://computologo.vila.bol.com.br E-mail - [EMAIL PROTECTED] "Tudo posso nAquele que me fortalece." Fp. 4:13 _______________________________________________________________________ Yahoo! GeoCities Tudo para criar o seu site: ferramentas f�ceis de usar, espa�o de sobra e acess�rios. http://br.geocities.yahoo.com/ -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
