: I'm not entirely convinced that it's related to our code, but it could be.
: Just trying to get a sense if other plugins have had similar problems, just
: by the nature of using Solr's resource loading from the /lib directory.
Plugins aren't something that every Solr users -- but enough people use
them that if there was a fundemental memory leak just from loading plugin
jars i'm guessing more people would be complaining.
I use plugins in several solr instances, and i've never noticed any
problems like you describe -- but i don't personally use tomcat.
Otis is right on the money: you need to use profiling tools to really look
at the heap and see what's taking up all that ram.
Alternately: a quick way to rule out the special plugin class loader would
be to embed your custom handler directly into the solr.war ("The Old Way"
on the SolrPlugins wiki) ... if you still have problems, then the cause
isn't the plugin classloader.
-Hoss
