# 11:07:17.097 \[Thread-4\] INFO nia.activedata.repository.ActiveDataRepository - listener timeout after waiting for \[30000\] ms

**URL:** <https://discuss.elastic.co/t/1117-097-thread-4-info-nia-activedata-repository-activedatarepository-listener-timeout-after-waiting-for-30000-ms/171567>\
**Category:** Elasticsearch\
**Created:** [March 8, 2019, 10:14pm UTC](https://discuss.elastic.co/t/1117-097-thread-4-info-nia-activedata-repository-activedatarepository-listener-timeout-after-waiting-for-30000-ms/171567 "2019-03-08T22:14:38Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![nikuland](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@nikuland](https://discuss.elastic.co/u/nikuland)\
**Post date:** [March 8, 2019, 10:14pm UTC](https://discuss.elastic.co/t/1117-097-thread-4-info-nia-activedata-repository-activedatarepository-listener-timeout-after-waiting-for-30000-ms/171567/1 "2019-03-08T22:14:38Z")

</div>

11:07:17.097 [Thread-4] INFO nia.activedata.repository.ActiveDataRepository - listener timeout after waiting for [30000] ms  
Get this problem even when i try to read data from elasicsearch

---

<div class="post-metadata">

**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:** [March 8, 2019, 11:04pm UTC](https://discuss.elastic.co/t/1117-097-thread-4-info-nia-activedata-repository-activedatarepository-listener-timeout-after-waiting-for-30000-ms/171567/2 "2019-03-08T23:04:16Z")

</div>

This trace is not coming from elasticsearch right?  
May be explain exactly what you are doing and how?

---

<div class="post-metadata">

**Author:** ![nikuland](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@nikuland](https://discuss.elastic.co/u/nikuland)\
**Post date:** [March 9, 2019, 12:12am UTC](https://discuss.elastic.co/t/1117-097-thread-4-info-nia-activedata-repository-activedatarepository-listener-timeout-after-waiting-for-30000-ms/171567/3 "2019-03-09T00:12:17Z")

</div>

i thought this is coming from elatic search. This is in java client, let me paste you the code  
**public** SearchResponse executeRequest(SearchRequest searchRequest) {

SearchResponse response = **null** ;

**try** {

response = restHighLevelClient.search(searchRequest);

} **catch** (Exception ee) {

_logger_ .info(ee.getMessage());

}

ee.getMessage give this message. I am thining this is comng from rest client

---

<div class="post-metadata">

**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:** [March 9, 2019, 4:58am UTC](https://discuss.elastic.co/t/1117-097-thread-4-info-nia-activedata-repository-activedatarepository-listener-timeout-after-waiting-for-30000-ms/171567/4 "2019-03-09T04:58:30Z")

</div>

This message comes from your java application which prints an elasticsearch message.

So we now know a little more. You are writing a java application using the rest client.

Do you think you can share more meaningful information?

Like elasticsearch version? How you create the client? Elasticsearch server full logs...?  
There's barely no way to help if you just paste a message like `listener timeout after waiting for [30000] ms`.

Also please format your code, logs or configuration files using `</>` icon as explained in [this guide](https://discuss.elastic.co/t/about-the-elasticsearch-category/21) and not the citation button. It will make your post more readable.

Or use markdown style like:

````
```
CODE
```

````

This is the icon to use if you are not using markdown format:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/e/7e6e239431ec2d71cbf1beef741f2e93e7cc762c.jpg)

There's a live preview panel for exactly this reasons.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.  
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.  
Please update your post.

---

<div class="post-metadata">

**Author:** ![nikuland](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@nikuland](https://discuss.elastic.co/u/nikuland)\
**Post date:** [March 11, 2019, 6:01am UTC](https://discuss.elastic.co/t/1117-097-thread-4-info-nia-activedata-repository-activedatarepository-listener-timeout-after-waiting-for-30000-ms/171567/5 "2019-03-11T06:01:49Z")

</div>

```
indent preformatted text by 4 spaces

```

elastic version 6.1.4. High level rest client is what we are using right now. Rest java client is created by using below lines  
restHighLevelClient = new RestHighLevelClient(  
RestClient.builder(  
new HttpHost(EsHost, 9200, "http")));

do u see any isssues with this

---

<div class="post-metadata">

**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:** [March 11, 2019, 7:26am UTC](https://discuss.elastic.co/t/1117-097-thread-4-info-nia-activedata-repository-activedatarepository-listener-timeout-after-waiting-for-30000-ms/171567/6 "2019-03-11T07:26:26Z")

</div>

> [@nikuland](#):
>
> do u see any isssues with this

No. I don't.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 8, 2019, 7:26am UTC](https://discuss.elastic.co/t/1117-097-thread-4-info-nia-activedata-repository-activedatarepository-listener-timeout-after-waiting-for-30000-ms/171567/7 "2019-04-08T07:26:28Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.