# Message not fully read for "analyze" **URL:** \ **Category:** Elasticsearch\ **Created:** [July 19, 2011, 11:57am UTC](https://discuss.elastic.co/t/message-not-fully-read-for-analyze/4895 "2011-07-19T11:57:55Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![melix](https://avatars.discourse-cdn.com/v4/letter/m/b38774/32.png) [@melix](https://discuss.elastic.co/u/melix)\ **Post date:** [July 19, 2011, 11:57am UTC](https://discuss.elastic.co/t/message-not-fully-read-for-analyze/4895/1 "2011-07-19T11:57:55Z")
Hi, I'm using the following code to send an analyze query : | final IndicesAdminClient indices = client.admin().indices(); final AnalyzeRequestBuilder analyzeRequestBuilder = indices.prepareAnalyze(index, text); analyzeRequestBuilder.field(field); final AnalyzeResponse analyzeResponse = analyzeRequestBuilder.execute().actionGet();| It works, but my log files are full of those warnings : |WARN : org.elasticsearch.transport.netty - [Shola Inkosi] Message not fully read (response) for [602] handler org.elasticsearch.client.transport.action.support.BaseClientTransportAction$1@1091857, error [false], resetting | I'm using ElasticSearch 0.17.0 on both client and server side. Any idea of what could cause this ? Thanks, Cédric ---
**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:** [July 19, 2011, 9:21pm UTC](https://discuss.elastic.co/t/message-not-fully-read-for-analyze/4895/2 "2011-07-19T21:21:31Z")
Are you sure you are using 0.17 on both client and server? This is explained by different versions used... On Tue, Jul 19, 2011 at 2:57 PM, Cédric Champeau \< [cedric.champeau@lingway.com](mailto:cedric.champeau@lingway.com)\> wrote: > \*\* > Hi, > > I'm using the following code to send an analyze query : > > ``` > final IndicesAdminClient indices = client.admin().indices(); > final AnalyzeRequestBuilder analyzeRequestBuilder = > > ``` > > indices.prepareAnalyze(index, text); > analyzeRequestBuilder.field(field); > final AnalyzeResponse analyzeResponse = > analyzeRequestBuilder.execute().actionGet(); > > It works, but my log files are full of those warnings : > > WARN : org.elasticsearch.transport.netty - [Shola Inkosi] Message not fully > read (response) for [602] handler > org.elasticsearch.client.transport.action.support.BaseClientTransportAction$1@1091857, > error [false], resetting > > I'm using Elasticsearch 0.17.0 on both client and server side. Any idea of > what could cause this ? > > Thanks, > > Cédric ---
**Author:** ![melix](https://avatars.discourse-cdn.com/v4/letter/m/b38774/32.png) [@melix](https://discuss.elastic.co/u/melix)\ **Post date:** [July 20, 2011, 7:18am UTC](https://discuss.elastic.co/t/message-not-fully-read-for-analyze/4895/3 "2011-07-20T07:18:04Z")
Yes, I'm totally sure : I have only one node plus a transport client. I reverted back to 0.16.4 (on both sides) and I have the same behaviour, so this doesn't look like a regression in 0.17.0. I only have this error message for analyze queries. Le 19/07/2011 23:21, Shay Banon a écrit : > Are you sure you are using 0.17 on both client and server? This is > explained by different versions used... > > On Tue, Jul 19, 2011 at 2:57 PM, Cédric Champeau > \<[cedric.champeau@lingway.com](mailto:cedric.champeau@lingway.com) [mailto:cedric.champeau@lingway.com](mailto:cedric.champeau@lingway.com)\> wrote: > > ``` > Hi, > > I'm using the following code to send an analyze query : > > | final IndicesAdminClient indices = client.admin().indices(); > final AnalyzeRequestBuilder analyzeRequestBuilder = > indices.prepareAnalyze(index, text); > analyzeRequestBuilder.field(field); > final AnalyzeResponse analyzeResponse = > analyzeRequestBuilder.execute().actionGet();| > > It works, but my log files are full of those warnings : > > |WARN : org.elasticsearch.transport.netty - [Shola Inkosi] Message > not fully read (response) for [602] handler > org.elasticsearch.client.transport.action.support.BaseClientTransportAction$1@1091857, > error [false], resetting > | > I'm using ElasticSearch 0.17.0 on both client and server side. Any > idea of what could cause this ? > > Thanks, > > Cédric > > ``` ---
**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:** [July 20, 2011, 7:05pm UTC](https://discuss.elastic.co/t/message-not-fully-read-for-analyze/4895/4 "2011-07-20T19:05:45Z")
ok, foudn the problem and opened an issue: [Analyze API: Failure to read full message over the wire · Issue #1138 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1138). On Wed, Jul 20, 2011 at 10:18 AM, Cédric Champeau \< [cedric.champeau@lingway.com](mailto:cedric.champeau@lingway.com)\> wrote: > \*\* > Yes, I'm totally sure : I have only one node plus a transport client. I > reverted back to 0.16.4 (on both sides) and I have the same behaviour, so > this doesn't look like a regression in 0.17.0. I only have this error > message for analyze queries. > > Le 19/07/2011 23:21, Shay Banon a écrit : > > Are you sure you are using 0.17 on both client and server? This is > explained by different versions used... > > On Tue, Jul 19, 2011 at 2:57 PM, Cédric Champeau \< > [cedric.champeau@lingway.com](mailto:cedric.champeau@lingway.com)\> wrote: > > > Hi, > > > > I'm using the following code to send an analyze query : > > > > ``` > > final IndicesAdminClient indices = client.admin().indices(); > > final AnalyzeRequestBuilder analyzeRequestBuilder = > > > > ``` > > > > indices.prepareAnalyze(index, text); > > analyzeRequestBuilder.field(field); > > final AnalyzeResponse analyzeResponse = > > analyzeRequestBuilder.execute().actionGet(); > > > > It works, but my log files are full of those warnings : > > > > WARN : org.elasticsearch.transport.netty - [Shola Inkosi] Message not > > fully read (response) for [602] handler > > org.elasticsearch.client.transport.action.support.BaseClientTransportAction$1@1091857, > > error [false], resetting > > > > I'm using Elasticsearch 0.17.0 on both client and server side. Any idea of > > what could cause this ? > > > > Thanks, > > > > Cédric ---
**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:59am UTC](https://discuss.elastic.co/t/message-not-fully-read-for-analyze/4895/5 "2017-07-06T03:59:59Z")
Closed on July 6, 2017, 3:59am UTC