After hitting the jsp once and then reloading the app, I ran Find leaks
through the manager application at http://localhost:8080/manager/html and
get this:

   The following web applications were stopped (reloaded, undeployed), but their
   classes from previous runs are still loaded in memory, thus causing a memory
   leak (use a profiler to confirm):
   /dynam

The name of the web app context is dynam.  Each time I repeat, I get
an extra /dynam line, as expected.  Additionally, each time I reload
the context catalina.out shows:

   SEVERE: The web application [/dynam] appears to have started a thread
named
   [IPC Client (1622444498) connection to hb02/192.168.200.102:60020 from
tslazar]
   but has failed to stop it. This is very likely to create a memory leak.

Is there a ZooKeeper method I should call to shutdown a thread?  I added a
finally block though that doesn't change the behavior.
On Mon, Mar 3, 2014 at 8:55 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB