Hi Michael, Yes, we do intend to reload Solr when deploying new cores. So we deploy it, update solr.xml and then restart Solr only. So this will happen sometimes in production, but mostly testing. Which means it will be a real pain. Any way to fix this?
Also, I'm running geronimo with -Xmx1024m -XX:MaxPermSize=256m. Regards, Marcos On Feb 6, 2013, at 10:54 AM, Michael Della Bitta wrote: > Marcos, > > The later 3 errors are common and won't pose a problem unless you > intend to reload the Solr application without restarting Geronimo > often. > > The first error, however, shouldn't happen. Have you changed the size > of PermGen at all? I noticed this error while testing Solr 4.0 in > Tomcat, but haven't seen it with Solr 4.1 (yet), so if you're on 4.0, > you might want to try upgrading. > > > Michael Della Bitta > > ------------------------------------------------ > Appinions > 18 East 41st Street, 2nd Floor > New York, NY 10017-6271 > > www.appinions.com > > Where Influence Isn’t a Game > > > On Wed, Feb 6, 2013 at 6:09 AM, Marcos Mendez <mar...@jitisoft.com> wrote: >> Hi, >> >> I'm deploying the SOLR war in Geronimo, with multiple cores. I'm seeing the >> following issue and it eats up a lot of memory when shutting down. Has >> anyone seen this and have an idea how to solve it? >> >> Exception in thread "DefaultThreadPool 196" java.lang.OutOfMemoryError: >> PermGen space >> 2013-02-05 20:13:34,747 ERROR [ConcurrentLRUCache] ConcurrentLRUCache was >> not destroyed prior to finalize(), indicates a bug -- POSSIBLE RESOURCE >> LEAK!!! >> 2013-02-05 20:13:34,747 ERROR [ConcurrentLRUCache] ConcurrentLRUCache was >> not destroyed prior to finalize(), indicates a bug -- POSSIBLE RESOURCE >> LEAK!!! >> 2013-02-05 20:13:34,747 ERROR [CoreContainer] CoreContainer was not >> shutdown prior to finalize(), indicates a bug -- POSSIBLE RESOURCE LEAK!!! >> instance=2080324477 >> >> Regards, >> Marcos
