# Still having problem with log4j on ES 5.1 with Storm1.0.2

**URL:** <https://discuss.elastic.co/t/still-having-problem-with-log4j-on-es-5-1-with-storm1-0-2/70302>\
**Category:** Elasticsearch\
**Created:** [December 30, 2016, 10:19pm UTC](https://discuss.elastic.co/t/still-having-problem-with-log4j-on-es-5-1-with-storm1-0-2/70302 "2016-12-30T22:19:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cynosureabu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cynosureabu/32/47196_2.png) [@cynosureabu](https://discuss.elastic.co/u/cynosureabu)\
**Post date:** [December 30, 2016, 10:19pm UTC](https://discuss.elastic.co/t/still-having-problem-with-log4j-on-es-5-1-with-storm1-0-2/70302/1 "2016-12-30T22:19:33Z")

</div>

Seems ES.5 has a hard dependency on a higher version of log4j than the one used in Storm.1: Storm is using  
log4j 2.1\*

If in pom i add log4j 2.7

 org.apache.logging.log4j log4j-api 2.7 org.apache.logging.log4j log4j-core 2.7

Then storm won't be started. I also tried copy 2.7ing jar to storm classPath, it didnt throw any error, but the topology cannot be started.

How can I get around this issue?

Chen

---

<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:** [January 27, 2017, 10:19pm UTC](https://discuss.elastic.co/t/still-having-problem-with-log4j-on-es-5-1-with-storm1-0-2/70302/2 "2017-01-27T22:19:52Z")

</div>

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