2012/11/7 Christopher Schultz <ch...@christopherschultz.net>: > >> I do not know about the dbcp one. It might be an issue. It >> certainly will contain a stack trace (it is what it is used for). >> I usually run with logAbandoned being turned off. Do you have >> opened connections in your pool? Do you have closeMethod="close" on >> your pool definition? > > Here's my <Resource>: > <Resource name="..." > description="..." > auth="Container" > type="javax.sql.DataSource" > maxActive="1" > maxIdle="1" > maxWait="10000" > url="..." > username="..." > password="..." > driverClassName="com.mysql.jdbc.Driver" > removeAbandoned="true" > removeAbandonedTimeout="30" > logAbandoned="true" > testOnBorrow="true" > validationQuery="/* ping */ SELECT 1" > /> > > So, I have no closeMethod defined for my <Resource>, so I suspect that > I get the default. I couldn't find any documentation on DBCP > closeMethod :( >
It is an attribute used by Tomcat itself, not DBCP: http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Resource_Definitions (FIXME: should be mentioned here as well, as well as the "singleton" attribute: http://tomcat.apache.org/tomcat-7.0-doc/config/globalresources.html#Resource_Definitions ) > I'm happy to provide a memory snapshot or even a screenshot ... You are on your own with this. I would not have much time to dig into this further. Maybe others can help. I think those chains of weak references are not an issue. Maybe you could remove parts of your configuration, of your webapp, until you have some minimal configuration that still reproduces the issue? Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
