# Java API ping operation hangs the application on Elasticsearch 7.11.0

**URL:** <https://discuss.elastic.co/t/java-api-ping-operation-hangs-the-application-on-elasticsearch-7-11-0/264351>\
**Category:** Elasticsearch\
**Created:** [February 15, 2021, 6:59pm UTC](https://discuss.elastic.co/t/java-api-ping-operation-hangs-the-application-on-elasticsearch-7-11-0/264351 "2021-02-15T18:59:48Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 17, 2021, 8:23am UTC](https://discuss.elastic.co/t/java-api-ping-operation-hangs-the-application-on-elasticsearch-7-11-0/264351/21 "2021-02-17T08:23:12Z")

</div>

It's a good question, I also don't have an immediate explanation. I wonder if those refreshes are not returning fast enough, so they're consuming the entire pool of connections. I'd try getting trace logging from the `org.apache.http` tree because I think that would answer this sort of question.

---

<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:** [March 17, 2021, 8:23am UTC](https://discuss.elastic.co/t/java-api-ping-operation-hangs-the-application-on-elasticsearch-7-11-0/264351/22 "2021-03-17T08:23:53Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/java-api-ping-operation-hangs-the-application-on-elasticsearch-7-11-0/264351.md?page=1)