# Tomcat / webapp with ES embedded in eclipse (debug mode) **URL:** \ **Category:** Elasticsearch\ **Created:** [January 4, 2012, 8:50pm UTC](https://discuss.elastic.co/t/tomcat-webapp-with-es-embedded-in-eclipse-debug-mode/6287 "2012-01-04T20:50:59Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [January 4, 2012, 8:50pm UTC](https://discuss.elastic.co/t/tomcat-webapp-with-es-embedded-in-eclipse-debug-mode/6287/1 "2012-01-04T20:50:59Z")
Hi there, I'm playing with an embedded ES node in a webapp deployed in a tomcat container. ES Node is injected using Spring. ES is 0.18.5 Tomcat is 7.0.19 Spring is 3.1.0.RELEASE And I'm launching everything in debug mode from Eclipse. Everything works fine for the "first launch" but each time tomcat restarts (because something changes in my workspace), it seems that Elasticsearch is not fully "unloaded" before the reload. So I quickly get OOM errors. When I look at the running threads, I can see at the first launch one occurrence of Daemon Thread [org.elasticsearch.common.base.internal.Finalizer] (Running) After one restart, I can see two of them, and after the third restart, a third occurrence. It seems to be the only Thread that remains after a Client.close() and Node.close(). Any idea ? Do I have to call another ES method to "destroy" all the ES threads ??? Anything I can do to add more details about this ? Thanks, David. ---
**Author:** ![plaflamme](https://avatars.discourse-cdn.com/v4/letter/p/a88e57/32.png) [@plaflamme](https://discuss.elastic.co/u/plaflamme)\ **Post date:** [January 5, 2012, 4:03am UTC](https://discuss.elastic.co/t/tomcat-webapp-with-es-embedded-in-eclipse-debug-mode/6287/2 "2012-01-05T04:03:52Z")
Seems to be the Guava "Finalizer" thread issue: > > > \_\[Original issue\](https://code.google.com/p/guava-libraries/issues/detail?id=92)… created by \*\*nairb774\*\* on 2008-07-28 at 05:39 PM\_ > > \--- > > If the class loader which loaded the google-collections jar is let go > (consider redeploying a war to Apache Geronimo) the class loader will not > be able to be garbage collected. This is caused by the thread started by > FinalizableReferenceQueue never ending. In other words the garbage > collection (for the class loader) can only happen when the thread stops. > The solution is to stop the thread when there are no more objects on the > queue. This will happen eventually if the rest of the app behaves > correctly by not placing state outside of its class loader's environment. > Attached is a version of the class which I have used to this effect. > > This is also a problem in the OSGi space where every jar gets its own class > loader and they can be refreshed easily at runtime to do rolling > upgrades/bug fixes. Philippe On Wed, Jan 4, 2012 at 15:50, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > Hi there,\*\*\*\* > > * * * > > * * * > > I’m playing with an embedded ES node in a webapp deployed in a tomcat > container.\*\*\*\* > > ES Node is injected using Spring.\*\*\*\* > > * * * > > ES is 0.18.5\*\*\*\* > > Tomcat is 7.0.19\*\*\*\* > > Spring is 3.1.0.RELEASE\*\*\*\* > > * * * > > And I’m launching everything in debug mode from Eclipse.\*\*\*\* > > * * * > > Everything works fine for the “first launch” but each time tomcat restarts > (because something changes in my workspace), it seems that Elasticsearch is > not fully “unloaded” before the reload.\*\*\*\* > > * * * > > So I quickly get OOM errors.\*\*\*\* > > * * * > > When I look at the running threads, I can see at the first launch one > occurrence of \*\*\*\* > > Daemon Thread [org.elasticsearch.common.base.internal.Finalizer] (Running) > > * * * > > * * * > > After one restart, I can see two of them, and after the third restart, a > third occurrence.\*\*\*\* > > * * * > > It seems to be the only Thread that remains after a Client.close() and > Node.close().\*\*\*\* > > * * * > > * * * > > Any idea ? Do I have to call another ES method to “destroy” all the ES > threads ???\*\*\*\* > > Anything I can do to add more details about this ?\*\*\*\* > > * * * > > Thanks,\*\*\*\* > > David. \*\*\*\* ---
**Author:** ![Michael\_Sick](https://avatars.discourse-cdn.com/v4/letter/m/22d042/32.png) [@Michael\_Sick](https://discuss.elastic.co/u/Michael_Sick)\ **Post date:** [January 5, 2012, 4:56am UTC](https://discuss.elastic.co/t/tomcat-webapp-with-es-embedded-in-eclipse-debug-mode/6287/3 "2012-01-05T04:56:34Z")
Wow what a thread! I see this behavior as well. Anyone have a workaround? On Wed, Jan 4, 2012 at 11:03 PM, Philippe Laflamme \< [philippe.laflamme@obiba.org](mailto:philippe.laflamme@obiba.org)\> wrote: > Seems to be the Guava "Finalizer" thread issue: > > [FinalizableReferenceQueue keeps ClassLoaders around. · Issue #92 · google/guava · GitHub](http://code.google.com/p/guava-libraries/issues/detail?id=92) > > Philippe > > On Wed, Jan 4, 2012 at 15:50, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > > > Hi there,\*\*\*\* > > > > * * * > > > > * * * > > > > I’m playing with an embedded ES node in a webapp deployed in a tomcat > > container.\*\*\*\* > > > > ES Node is injected using Spring.\*\*\*\* > > > > * * * > > > > ES is 0.18.5\*\*\*\* > > > > Tomcat is 7.0.19\*\*\*\* > > > > Spring is 3.1.0.RELEASE\*\*\*\* > > > > * * * > > > > And I’m launching everything in debug mode from Eclipse.\*\*\*\* > > > > * * * > > > > Everything works fine for the “first launch” but each time tomcat > > restarts (because something changes in my workspace), it seems that > > Elasticsearch is not fully “unloaded” before the reload.\*\*\*\* > > > > * * * > > > > So I quickly get OOM errors.\*\*\*\* > > > > * * * > > > > When I look at the running threads, I can see at the first launch one > > occurrence of \*\*\*\* > > > > Daemon Thread [org.elasticsearch.common.base.internal.Finalizer] (Running) > > > > * * * > > > > * * * > > > > After one restart, I can see two of them, and after the third restart, a > > third occurrence.\*\*\*\* > > > > * * * > > > > It seems to be the only Thread that remains after a Client.close() and > > Node.close().\*\*\*\* > > > > * * * > > > > * * * > > > > Any idea ? Do I have to call another ES method to “destroy” all the ES > > threads ???\*\*\*\* > > > > Anything I can do to add more details about this ?\*\*\*\* > > > > * * * > > > > Thanks,\*\*\*\* > > > > David. \*\*\*\* ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [January 5, 2012, 1:55pm UTC](https://discuss.elastic.co/t/tomcat-webapp-with-es-embedded-in-eclipse-debug-mode/6287/4 "2012-01-05T13:55:25Z")
Can you try and set index.cache.query.parser.type to none when you start the node in its settings? Thats the only place that uses weak cache. On Thu, Jan 5, 2012 at 6:56 AM, Michael Sick \< [michael.sick@serenesoftware.com](mailto:michael.sick@serenesoftware.com)\> wrote: > Wow what a thread! I see this behavior as well. Anyone have a workaround? > > On Wed, Jan 4, 2012 at 11:03 PM, Philippe Laflamme \< > [philippe.laflamme@obiba.org](mailto:philippe.laflamme@obiba.org)\> wrote: > > > Seems to be the Guava "Finalizer" thread issue: > > > > [FinalizableReferenceQueue keeps ClassLoaders around. · Issue #92 · google/guava · GitHub](http://code.google.com/p/guava-libraries/issues/detail?id=92) > > > > Philippe > > > > On Wed, Jan 4, 2012 at 15:50, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > > > > > Hi there,\*\*\*\* > > > > > > * * * > > > > > > * * * > > > > > > I’m playing with an embedded ES node in a webapp deployed in a tomcat > > > container.\*\*\*\* > > > > > > ES Node is injected using Spring.\*\*\*\* > > > > > > * * * > > > > > > ES is 0.18.5\*\*\*\* > > > > > > Tomcat is 7.0.19\*\*\*\* > > > > > > Spring is 3.1.0.RELEASE\*\*\*\* > > > > > > * * * > > > > > > And I’m launching everything in debug mode from Eclipse.\*\*\*\* > > > > > > * * * > > > > > > Everything works fine for the “first launch” but each time tomcat > > > restarts (because something changes in my workspace), it seems that > > > Elasticsearch is not fully “unloaded” before the reload.\*\*\*\* > > > > > > * * * > > > > > > So I quickly get OOM errors.\*\*\*\* > > > > > > * * * > > > > > > When I look at the running threads, I can see at the first launch one > > > occurrence of \*\*\*\* > > > > > > Daemon Thread [org.elasticsearch.common.base.internal.Finalizer] > > > (Running)\*\*\*\* > > > > > > * * * > > > > > > After one restart, I can see two of them, and after the third restart, a > > > third occurrence.\*\*\*\* > > > > > > * * * > > > > > > It seems to be the only Thread that remains after a Client.close() and > > > Node.close().\*\*\*\* > > > > > > * * * > > > > > > * * * > > > > > > Any idea ? Do I have to call another ES method to “destroy” all the ES > > > threads ???\*\*\*\* > > > > > > Anything I can do to add more details about this ?\*\*\*\* > > > > > > * * * > > > > > > Thanks,\*\*\*\* > > > > > > David. \*\*\*\* ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [January 5, 2012, 4:53pm UTC](https://discuss.elastic.co/t/tomcat-webapp-with-es-embedded-in-eclipse-debug-mode/6287/5 "2012-01-05T16:53:25Z")
I put index.cache.query.parser.type=none in the same file where I defined the clustername and it didn't change the behaviour. I can always see one, two then 3 threads org.elasticsearch.common.base.internal.Finalizer and I finally get OOM issues. Finalizer seems to be one of the first threads launched by ES. My es property file contains only : cluster.name=es-search discovery.zen.ping.multicast.enabled=false index.cache.query.parser.type=none David. Le 5 janvier 2012 à 14:55, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) a écrit : > Can you try and set index.cache.query.parser.type to none when you start the > node in its settings? Thats the only place that uses weak cache. > > On Thu, Jan 5, 2012 at 6:56 AM, Michael Sick\<[michael.sick@serenesoftware.com](mailto:michael.sick@serenesoftware.com) > [[mailto:michael.sick@serenesoftware.com](mailto:michael.sick@serenesoftware.com)] \>wrote: > > > Wow what a thread! I see this behavior as well. Anyone have a workaround? > > > > On Wed, Jan 4, 2012 at 11:03 PM, Philippe > > Laflamme\<[philippe.laflamme@obiba.org](mailto:philippe.laflamme@obiba.org) [[mailto:philippe.laflamme@obiba.org](mailto:philippe.laflamme@obiba.org)] > > > > > wrote: > > > > > Seems to be the Guava "Finalizer" thread issue: > > > > > > [FinalizableReferenceQueue keeps ClassLoaders around. · Issue #92 · google/guava · GitHub](http://code.google.com/p/guava-libraries/issues/detail?id=92) > > > > > > Philippe > > > > > > On Wed, Jan 4, 2012 at 15:50, David Pilato\<[david@pilato.fr](mailto:david@pilato.fr) > > > [[mailto:david@pilato.fr](mailto:david@pilato.fr)] \>wrote: > > > > > > > Hi there, > > > > > > > > I’m playing with an embedded ES node in a webapp deployed in a tomcat > > > > container. > > > > ES Node is injected using Spring. > > > > > > > > ES is 0.18.5 > > > > Tomcat is 7.0.19 > > > > Spring is 3.1.0.RELEASE > > > > > > > > And I’m launching everything in debug mode from Eclipse. > > > > > > > > Everything works fine for the “first launch” but each time tomcat > > > > restarts (because something changes in my workspace), it seems that > > > > Elasticsearch is not fully “unloaded” before the reload. > > > > > > > > So I quickly get OOM errors. > > > > > > > > When I look at the running threads, I can see at the first launch one > > > > occurrence of > > > > Daemon Thread [org.elasticsearch.common.base.internal.Finalizer] > > > > (Running) > > > > > > > > After one restart, I can see two of them, and after the third restart, a > > > > third occurrence. > > > > > > > > It seems to be the only Thread that remains after a Client.close() and > > > > Node.close(). > > > > > > > > Any idea ? Do I have to call another ES method to “destroy” all the ES > > > > threads ??? > > > > Anything I can do to add more details about this ? > > > > > > > > Thanks, > > > > David. -- David Pilato [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) Twitter : @dadoonet ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [January 6, 2012, 11:31am UTC](https://discuss.elastic.co/t/tomcat-webapp-with-es-embedded-in-eclipse-debug-mode/6287/6 "2012-01-06T11:31:42Z")
I will double check in 0.18, master not longer has this problem, btw, because of different usage of Cache guava (and new versions of guava). On Thu, Jan 5, 2012 at 6:53 PM, [david@pilato.fr](mailto:david@pilato.fr) [david@pilato.fr](mailto:david@pilato.fr) wrote: > \*\* > > I put index.cache.query.parser.type=none in the same file where I defined > the clustername and it didn't change the behaviour. > > I can always see one, two then 3 > threads org.elasticsearch.common.base.internal.Finalizer and I finally get > OOM issues. > > Finalizer seems to be one of the first threads launched by ES. > > My es property file contains only : > > cluster.name=es-search discovery.zen.ping.multicast.enabled=false > > index.cache.query.parser.type=none > > David. > > Le 5 janvier 2012 à 14:55, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) a écrit : > > Can you try and set index.cache.query.parser.type to none when you start > the node in its settings? Thats the only place that uses weak cache. > > On Thu, Jan 5, 2012 at 6:56 AM, Michael Sick \< > [michael.sick@serenesoftware.com](mailto:michael.sick@serenesoftware.com) \> wrote: > > Wow what a thread! I see this behavior as well. Anyone have a workaround? > > On Wed, Jan 4, 2012 at 11:03 PM, Philippe Laflamme \< > [philippe.laflamme@obiba.org](mailto:philippe.laflamme@obiba.org) \> wrote: > > Seems to be the Guava "Finalizer" thread issue: > > [FinalizableReferenceQueue keeps ClassLoaders around. · Issue #92 · google/guava · GitHub](http://code.google.com/p/guava-libraries/issues/detail?id=92) > > Philippe > > On Wed, Jan 4, 2012 at 15:50, David Pilato \< [david@pilato.fr](mailto:david@pilato.fr) \> wrote: > > Hi there, > > I’m playing with an embedded ES node in a webapp deployed in a tomcat > container. > > ES Node is injected using Spring. > > ES is 0.18.5 > > Tomcat is 7.0.19 > > Spring is 3.1.0.RELEASE > > And I’m launching everything in debug mode from Eclipse. > > Everything works fine for the “first launch” but each time tomcat restarts > (because something changes in my workspace), it seems that Elasticsearch is > not fully “unloaded” before the reload. > > So I quickly get OOM errors. > > When I look at the running threads, I can see at the first launch one > occurrence of > > Daemon Thread [org.elasticsearch.common.base.internal.Finalizer] (Running) > > After one restart, I can see two of them, and after the third restart, a > third occurrence. > > It seems to be the only Thread that remains after a Client.close() and > Node.close(). > > Any idea ? Do I have to call another ES method to “destroy” all the ES > threads ??? > > Anything I can do to add more details about this ? > > Thanks, > > David. > > -- > David Pilato > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > Twitter : @dadoonet ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [January 6, 2012, 12:42pm UTC](https://discuss.elastic.co/t/tomcat-webapp-with-es-embedded-in-eclipse-debug-mode/6287/7 "2012-01-06T12:42:13Z")
Ok that's fine for me. I can use 0.19.0-SNAPSHOT. I will test it and write results here. Thanks David 😉 @dadoonet Le 6 janv. 2012 à 12:31, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) a écrit : > I will double check in 0.18, master not longer has this problem, btw, because of different usage of Cache guava (and new versions of guava). > > On Thu, Jan 5, 2012 at 6:53 PM, [david@pilato.fr](mailto:david@pilato.fr) [david@pilato.fr](mailto:david@pilato.fr) wrote: > I put index.cache.query.parser.type=none in the same file where I defined the clustername and it didn't change the behaviour. > I can always see one, two then 3 threads org.elasticsearch.common.base.internal.Finalizer and I finally get OOM issues. > > Finalizer seems to be one of the first threads launched by ES. > > My es property file contains only : > cluster.name=es-search discovery.zen.ping.multicast.enabled=false > > index.cache.query.parser.type=none > > David. > > Le 5 janvier 2012 à 14:55, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) a écrit : > > Can you try and set index.cache.query.parser.type to none when you start the node in its settings? Thats the only place that uses weak cache. > > On Thu, Jan 5, 2012 at 6:56 AM, Michael Sick \< [michael.sick@serenesoftware.com](mailto:michael.sick@serenesoftware.com) \> wrote: > Wow what a thread! I see this behavior as well. Anyone have a workaround? > > On Wed, Jan 4, 2012 at 11:03 PM, Philippe Laflamme \< [philippe.laflamme@obiba.org](mailto:philippe.laflamme@obiba.org) \> wrote: > Seems to be the Guava "Finalizer" thread issue: > > [FinalizableReferenceQueue keeps ClassLoaders around. · Issue #92 · google/guava · GitHub](http://code.google.com/p/guava-libraries/issues/detail?id=92) > > Philippe > > On Wed, Jan 4, 2012 at 15:50, David Pilato \< [david@pilato.fr](mailto:david@pilato.fr) \> wrote: > Hi there, > > I’m playing with an embedded ES node in a webapp deployed in a tomcat container. > > ES Node is injected using Spring. > > ES is 0.18.5 > > Tomcat is 7.0.19 > > Spring is 3.1.0.RELEASE > > And I’m launching everything in debug mode from Eclipse. > > Everything works fine for the “first launch” but each time tomcat restarts (because something changes in my workspace), it seems that Elasticsearch is not fully “unloaded” before the reload. > > So I quickly get OOM errors. > > When I look at the running threads, I can see at the first launch one occurrence of > > Daemon Thread [org.elasticsearch.common.base.internal.Finalizer] (Running) > > After one restart, I can see two of them, and after the third restart, a third occurrence. > > It seems to be the only Thread that remains after a Client.close() and Node.close(). > > Any idea ? Do I have to call another ES method to “destroy” all the ES threads ??? > > Anything I can do to add more details about this ? > > Thanks, > > David. > > -- > David Pilato > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > Twitter : @dadoonet ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:43am UTC](https://discuss.elastic.co/t/tomcat-webapp-with-es-embedded-in-eclipse-debug-mode/6287/8 "2017-07-06T03:43:40Z")