# Remote data store with ElasticSearch 7.1 and log4j2.11.1

**URL:** <https://discuss.elastic.co/t/remote-data-store-with-elasticsearch-7-1-and-log4j2-11-1/183935>\
**Category:** Logstash\
**Created:** [June 3, 2019, 10:29am UTC](https://discuss.elastic.co/t/remote-data-store-with-elasticsearch-7-1-and-log4j2-11-1/183935 "2019-06-03T10:29:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joseph\_Schooling](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joseph_schooling/32/46488_2.png) [@Joseph\_Schooling](https://discuss.elastic.co/u/Joseph_Schooling)\
**Post date:** [June 3, 2019, 10:29am UTC](https://discuss.elastic.co/t/remote-data-store-with-elasticsearch-7-1-and-log4j2-11-1/183935/1 "2019-06-03T10:29:07Z")

</div>

Hi,

I am using ElasticSearch 7.1. It comes with log4j2.11.1.jar. The problem comes when I am trying to setup a remote data store with log4j2 running as a TcpSocketServer. I would then use log4j logging API in different Java applications to transmit logs over to the remote data store to analyse. However, from log4j2 Java documentation, I found out that the TcpSocketServer has been taken out.

How did you guys managed to configure a remote data store with the latest log4j2 library? Is there any working architecture layout which still fits my use case?

Thanks in advance,

Joseph

---

<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:** [July 1, 2019, 10:29am UTC](https://discuss.elastic.co/t/remote-data-store-with-elasticsearch-7-1-and-log4j2-11-1/183935/2 "2019-07-01T10:29:08Z")

</div>

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