-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 5/31/13 11:39 AM, Christopher Schultz wrote:
> - Using MySQL Connector/J 5.1.24 (important later) - Not running
> under a SecurityManager - has no "clearReferences...*"
> attributes set (all default to "false" save for
> HttpClientKeepAlive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
Also worth noting is that it appears only the first WebappClassLoader
is leaked: multiple subsequent webapp re-loads do not leak additional
WebappClassLoaders (which is kind of nice).
- -chris
On 5/31/13 2:10 PM, Christopher Schultz wrote:
>
Chuck,
On May 31, 2013, at 12:02, "Caldarale, Charles R"
wrote:
>> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>> Subject: WebappClassLoaders pinned in memory by
>> java.security.ProtectionDomain objects
>
>> Using MySQL Connector/J 5.1.24 (important later)
>
> Where is t
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: WebappClassLoaders pinned in memory by
> java.security.ProtectionDomain objects
> Using MySQL Connector/J 5.1.24 (important later)
Where is the JDBC jar located? Is the observed behavior different if it's in
tomcat/l
