# Elasticsearch Winlogbeats cause "caught exception while handling client http traffic"

**URL:** <https://discuss.elastic.co/t/elasticsearch-winlogbeats-cause-caught-exception-while-handling-client-http-traffic/246686>\
**Category:** Elasticsearch\
**Created:** [August 27, 2020, 8:51pm UTC](https://discuss.elastic.co/t/elasticsearch-winlogbeats-cause-caught-exception-while-handling-client-http-traffic/246686 "2020-08-27T20:51:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)\
**Post date:** [August 27, 2020, 8:51pm UTC](https://discuss.elastic.co/t/elasticsearch-winlogbeats-cause-caught-exception-while-handling-client-http-traffic/246686/1 "2020-08-27T20:51:40Z")

</div>

Hi All,

I was wondering if anyone has any help for what I'm seeing. I have about 150 winlogbeats pointing to a 3 node ES cluster. Over the course of about an hour, I get about 20,000 logs of:

```
caught exception while handling client http traffic, closing connection Netty4HttpChannel{localAddress=/<es_server_ip>, remoteAddress=/<remote_ip>:26577} o.e.h.AbstractHttpServerTransport

```

Is there something that can be done to reduce these logs? I feel like 20,000 logs an hour from 150 beats is a bit excessive.

From my Googling there were a few different things, but nothing really provided a solution from what I could find.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 31, 2020, 3:53am UTC](https://discuss.elastic.co/t/elasticsearch-winlogbeats-cause-caught-exception-while-handling-client-http-traffic/246686/2 "2020-08-31T03:53:20Z")

</div>

Where are you seeing those logs?

---

<div class="post-metadata">

**Author:** ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)\
**Post date:** [August 31, 2020, 1:37pm UTC](https://discuss.elastic.co/t/elasticsearch-winlogbeats-cause-caught-exception-while-handling-client-http-traffic/246686/3 "2020-08-31T13:37:30Z")

</div>

I was actually able to figure this out by looking further at the stacktrace and the issue came down to an incorrectly configured ca cert on the beats end. I was able to correct the ca and am no longer getting the error.

---

<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:** [September 28, 2020, 1:37pm UTC](https://discuss.elastic.co/t/elasticsearch-winlogbeats-cause-caught-exception-while-handling-client-http-traffic/246686/4 "2020-09-28T13:37:41Z")

</div>

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