-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
:
> 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 ob
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
> 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&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
My primary webapp (and ClassLoader) used to unload cleanly but now I
get WebappClassLoaders still stuck in memory after a reload. I'm
having a little trouble figuring out exactly what is holding onto
references. Here's what I know:
- - Tomcat
