tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edson Alves Pereira <eapere...@panamericano.com.br>
Subject RE: problems with dbcp
Date Mon, 03 Nov 2003 14:03:28 GMT
		But removeAbandoned and removeAbandonedTimeout doesn´t close
all ResultSet, Statement and Connections even if they are forsaken?


> ----------
> De: 	Florian Ebeling[SMTP:febeli@yahoo.de]
> Responder: 	Tomcat Users List
> Enviada: 	segunda-feira, 3 de novembro de 2003 9:51
> Para: 	Tomcat Users List
> Assunto: 	Re: problems with dbcp
> 
> Hi,
> 
> you probably do nor close some statement, resultSet or connection. When 
> using CP one has to do this always explicitly.
> 
> Tyrex is an alternative CP implementation which has been replaced by DBCP.
> 
> Edson Alves Pereira wrote:
> 
> > 	Hello folks, i followed what is written in tomcat-4.1.x´s JDNI
> > DataSource documentation, but i getting this error:
> > 
> > java.sql.SQLException: DBCP could not obtain an idle db connection, pool
> > exhausted
> > 
> > 	The machanism is not returning my connection to pool, what do i
> > should do? Do i really need tirex as Persistence Layer?  Here is my DBCP
> > configuration:
> > 
> > <Resource name="jdbc/OracleDS"
> > auth="Container"
> > type="javax.sql.DataSource"/>
> > <ResourceParams name="jdbc/OracleDS">
> > <parameter>
> > <name>factory</name>
> > <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
> > </parameter>       							
> > 
> > <parameter>
> > <name>maxActive</name>
> > <value>10</value>
> > </parameter>
> > 
> > 
> > <parameter>
> > <name>maxIdle</name>
> > <value>30</value>
> > </parameter>
> > 
> > <parameter>
> > <name>maxWait</name>
> > <value>10000</value>
> > </parameter>    						
> > 
> > <parameter>
> > <name>username</name>
> > <value>blah</value>
> > </parameter>
> > <parameter>
> > <name>password</name>
> > <value>blah</value>
> > </parameter>  
> > 
> > <parameter>
> > <name>driverClassName</name>
> > <value>oracle.jdbc.driver.OracleDriver</value>
> > </parameter>						
> > 
> > <parameter>
> > <name>url</name>
> > <value>jdbc:oracle:thin:@000.000.000:blah</value>
> > </parameter>
> > 
> > <parameter>
> > <name>validationQuery</name>
> > <value>select sysdate from dual</value>
> > </parameter>						
> > 
> > <parameter>
> > <name>removeAbandoned</name>
> > <value>true</value>
> > </parameter>        		
> > 
> > <parameter>
> > <name>removeAbandonedTimeout</name>
> > <value>60</value>
> > </parameter>
> > 
> > <parameter>
> > <name>logAbandoned</name>
> > <value>true</value>
> > </parameter>
> > </ResourceParams>
> > 
> > 	As i wrote above, DBCP should revover all connection objects and
> > close automatic everything, but is not. Any idea?
> > 
> > 	Regards,
> > 	Edson
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message