-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ziggy,
On 11/3/2010 9:44 AM, Ziggy wrote: > Hi All, > > <Resource name="myConn" auth="Container" > type="javax.sql.DataSource" > driverClassName="oracle.jdbc.driver.OracleDriver" > url="jdbc:oracle:thin:@10.10.10.10.:1521:mydb" > username="username" password="password" maxActive="500" > maxIdle="50" > maxWait="-1" removeAbandoned="true" > removeAbandonedTimeout="60" logAbandoned="true" > accessToUnderlyingConnectionAllowed="true" > /> > > I am trying to find out areas of the application where connections are NOT > being closed. I added the removeAbandoned and logAbandoned clauses in my > context file but if i check v$session on oracle it is still showing the same > number of connections active even after 60 seconds. Is there something wrong > in the configuration above? Tip: try setting maxActive="1" in development. You'll run across connection leaks much faster that way. > How exactly does it abandone the connections? what triggers it>? Read (the end of the) configuration docs for commons-dbcp, which is the basis for connection pooling in Tomcat: http://commons.apache.org/dbcp/configuration.html - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzRaN8ACgkQ9CaO5/Lv0PDstgCfYQAuiuuVkY2Rn8yb5S9sejNI SUcAn0ZeJN6rceOFscp8DncfdReqSAYK =QFUQ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
