# Java TransportClient Memory Leak
**URL:** https://discuss.elastic.co/t/java-transportclient-memory-leak/11157
**Category:** Elasticsearch
**Created:** [March 14, 2013, 1:57pm UTC](https://discuss.elastic.co/t/java-transportclient-memory-leak/11157 "2013-03-14T13:57:45Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@kelaban](https://discuss.elastic.co/u/kelaban)
#### Post date: [March 14, 2013, 1:57pm UTC](https://discuss.elastic.co/t/java-transportclient-memory-leak/11157/1 "2013-03-14T13:57:45Z")
I've had an ongoing problem using the Java TransportClient injected through
elasticsearch-spring. When trying to load test my client once I hit the
180k request mark requests start to hang, some take 20+ seconds. I've load
tested the elasticsearch directly to make sure it wasn't a configuration
problem over there. When I kill my load test if I start it up again it
picks up just as slow until I restart my client. After checking the GC logs
fingers point to memory being used up.
This is how I am doing my search:
```
String escapedQuery = LUCENE_PATTERN.matcher(params.getQuery()).
```
replaceAll(REPLACEMENT\_STRING);
```
SearchRequestBuilder theSearch = esClient.prepareSearch(THE_INDEX)
.setSearchType(SearchType.QUERY_THEN_FETCH);
theSearch.addFields(params.getAsStringArray(params.getReturnFields
```
()));
```
QueryBuilder theQuery = QueryBuilders.queryString(escapedQuery)
.field(TICKER_FIELD)
.field(NAME_FIELD)
.analyzer(WHITESPACE_ANALYZER)
.useDisMax(true)
.defaultOperator(QueryStringQueryBuilder.Operator.AND);
theSearch.setQuery(theQuery)
.setSize(params.getSize())
.setFrom(params.getFrom());
SearchResponse resp = theSearch.execute().actionGet();
```
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@kelaban](https://discuss.elastic.co/u/kelaban)
#### Post date: [March 14, 2013, 1:58pm UTC](https://discuss.elastic.co/t/java-transportclient-memory-leak/11157/2 "2013-03-14T13:58:38Z")
To clarify I am using ES v0.20.5
On Thursday, March 14, 2013 9:57:45 AM UTC-4, Keith L wrote:
> I've had an ongoing problem using the Java TransportClient injected
> through elasticsearch-spring. When trying to load test my client once I hit
> the 180k request mark requests start to hang, some take 20+ seconds. I've
> load tested the elasticsearch directly to make sure it wasn't a
> configuration problem over there. When I kill my load test if I start it up
> again it picks up just as slow until I restart my client. After checking
> the GC logs fingers point to memory being used up.
> This is how I am doing my search:
>
> ```
> String escapedQuery = LUCENE_PATTERN.matcher(params.getQuery()).
>
> ```
>
> replaceAll(REPLACEMENT\_STRING);
>
> ```
> SearchRequestBuilder theSearch = esClient.prepareSearch(THE_INDEX)
> .setSearchType(SearchType.QUERY_THEN_FETCH);
>
> theSearch.addFields(params.getAsStringArray(params.getReturnFields
>
> ```
>
> ()));
>
> ```
> QueryBuilder theQuery = QueryBuilders.queryString(escapedQuery)
> .field(TICKER_FIELD)
> .field(NAME_FIELD)
> .analyzer(WHITESPACE_ANALYZER)
> .useDisMax(true)
> .defaultOperator(QueryStringQueryBuilder.Operator.AND);
>
> theSearch.setQuery(theQuery)
> .setSize(params.getSize())
> .setFrom(params.getFrom());
>
> SearchResponse resp = theSearch.execute().actionGet();
>
> ```
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@kelaban](https://discuss.elastic.co/u/kelaban)
#### Post date: [March 14, 2013, 1:59pm UTC](https://discuss.elastic.co/t/java-transportclient-memory-leak/11157/3 "2013-03-14T13:59:28Z")
to clarify I am using ES v0.20.5
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@kelaban](https://discuss.elastic.co/u/kelaban)
#### Post date: [March 14, 2013, 2:02pm UTC](https://discuss.elastic.co/t/java-transportclient-memory-leak/11157/4 "2013-03-14T14:02:37Z")
to clarify I am using ES v0.20.5. And this is in a tomcat webapp
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [March 14, 2013, 2:22pm UTC](https://discuss.elastic.co/t/java-transportclient-memory-leak/11157/5 "2013-03-14T14:22:44Z")
Are you restarting your webapp (modify code _live_) instead of restarting Tomcat?
If so, it's due to a very old issue in Google guice as far as I remember. Some threads are not deleted and still here in the JVM when restarting the webapp.
--
David 😉
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 14 mars 2013 à 15:02, Keith L [kelaban17@gmail.com](mailto:kelaban17@gmail.com) a écrit :
> ## to clarify I am using ES v0.20.5. And this is in a tomcat webapp
>
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@kelaban](https://discuss.elastic.co/u/kelaban)
#### Post date: [March 14, 2013, 2:33pm UTC](https://discuss.elastic.co/t/java-transportclient-memory-leak/11157/6 "2013-03-14T14:33:17Z")
I think that's not the issue. When I restart the tomcat everything works as
expected again until I get to the 180k request mark at which point it
cannot handle anymore requests until the app is restarted again. The app
conks out at 180k almost on the mark every time regardless of stress
testing with 1 thread or 100 threads and always preforms the the same after
the webapp is restarted.
On Thursday, March 14, 2013 10:22:44 AM UTC-4, David Pilato wrote:
> Are you restarting your webapp (modify code _live_) instead of restarting
> Tomcat?
>
> If so, it's due to a very old issue in Google guice as far as I remember.
> Some threads are not deleted and still here in the JVM when restarting the
> webapp.
>
> --
> David 😉
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>
> Le 14 mars 2013 Ã 15:02, Keith L \<[kela...@gmail.com](mailto:kela...@gmail.com) \\> a
> écrit :
>
> to clarify I am using ES v0.20.5. And this is in a tomcat webapp
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \.
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@kelaban](https://discuss.elastic.co/u/kelaban)
#### Post date: [March 15, 2013, 5:08pm UTC](https://discuss.elastic.co/t/java-transportclient-memory-leak/11157/7 "2013-03-15T17:08:31Z")
Figured out the issue, turns out not to be elasticsearch. The default
tomcat session is set to 30 minutes which was taking up all the memory.
After fixing that issue the elasticsearch load test performed perfect.
On Thursday, March 14, 2013 10:33:17 AM UTC-4, Keith L wrote:
> I think that's not the issue. When I restart the tomcat everything works
> as expected again until I get to the 180k request mark at which point it
> cannot handle anymore requests until the app is restarted again. The app
> conks out at 180k almost on the mark every time regardless of stress
> testing with 1 thread or 100 threads and always preforms the the same after
> the webapp is restarted.
>
> On Thursday, March 14, 2013 10:22:44 AM UTC-4, David Pilato wrote:
>
> > Are you restarting your webapp (modify code _live_) instead of restarting
> > Tomcat?
> >
> > If so, it's due to a very old issue in Google guice as far as I remember.
> > Some threads are not deleted and still here in the JVM when restarting the
> > webapp.
> >
> > --
> > David 😉
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> >
> > Le 14 mars 2013 à 15:02, Keith L [kela...@gmail.com](mailto:kela...@gmail.com) a écrit :
> >
> > to clarify I am using ES v0.20.5. And this is in a tomcat webapp
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "elasticsearch" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [March 15, 2013, 5:14pm UTC](https://discuss.elastic.co/t/java-transportclient-memory-leak/11157/8 "2013-03-15T17:14:13Z")
Thanks for the update.
--
David 😉
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 15 mars 2013 à 18:08, Keith L [kelaban17@gmail.com](mailto:kelaban17@gmail.com) a écrit :
> Figured out the issue, turns out not to be elasticsearch. The default tomcat session is set to 30 minutes which was taking up all the memory. After fixing that issue the elasticsearch load test performed perfect.
>
> On Thursday, March 14, 2013 10:33:17 AM UTC-4, Keith L wrote:
>
> > I think that's not the issue. When I restart the tomcat everything works as expected again until I get to the 180k request mark at which point it cannot handle anymore requests until the app is restarted again. The app conks out at 180k almost on the mark every time regardless of stress testing with 1 thread or 100 threads and always preforms the the same after the webapp is restarted.
> >
> > On Thursday, March 14, 2013 10:22:44 AM UTC-4, David Pilato wrote:
> >
> > > Are you restarting your webapp (modify code _live_) instead of restarting Tomcat?
> > >
> > > If so, it's due to a very old issue in Google guice as far as I remember. Some threads are not deleted and still here in the JVM when restarting the webapp.
> > >
> > > --
> > > David 😉
> > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > >
> > > Le 14 mars 2013 à 15:02, Keith L [kela...@gmail.com](mailto:kela...@gmail.com) a écrit :
> > >
> > > > ## to clarify I am using ES v0.20.5. And this is in a tomcat webapp
> > > >
> > > > You received this message because you are subscribed to the Google Groups "elasticsearch" group.
> > > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).
> > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > --
> > > > You received this message because you are subscribed to the Google Groups "elasticsearch" group.
> > > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 2:46am UTC](https://discuss.elastic.co/t/java-transportclient-memory-leak/11157/9 "2017-07-06T02:46:16Z")