-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 André,
On 3/8/12 11:34 AM, André Warnier wrote: > Christopher Schultz wrote: >> It looks like the MBean (or maybe the pool itself) is exposing >> something that shouldn't be treated as a property: the >> connection itself. Calling getConnection (or, in this case, >> getXAConnection) will actually obtain a connection from the pool >> and will probably cause a minor connection leak (assuming >> "abandoned" settings are in place, you'll recover). These methods >> shouldn't be called by the MBeanDumper, and thus probably should >> be exposed as an attribute through an MBean. >> > You meant "should not be exposed", right ? Yes, I did. I checked the mbeans-deacriptor in trunk and there seems to be no mention of "connection" or "XAConnection" as attributes. I'll have to configure a jdbc-pool locally and take a look. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9ZCqQACgkQ9CaO5/Lv0PCNMgCeP77oDFUX9pTs2Mb505iBvUJA SGUAoL52SYknScw4tWdX5bBOhvzOZifm =+PgI -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
