# Wowza Core dumped after changes with log4j

**URL:** <https://community.wowza.com/t/wowza-core-dumped-after-changes-with-log4j/94321>\
**Category:** Wowza Streaming Engine\
**Tags:** wowza-streaming-engine\
**Created:** [December 14, 2021, 2:23pm UTC](https://community.wowza.com/t/wowza-core-dumped-after-changes-with-log4j/94321 "2021-12-14T14:23:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dan\_Donald](https://avatars.discourse-cdn.com/v4/letter/d/96bed5/32.png) [@Dan\_Donald](https://community.wowza.com/u/Dan_Donald)\
**Post date:** [December 14, 2021, 2:23pm UTC](https://community.wowza.com/t/wowza-core-dumped-after-changes-with-log4j/94321/1 "2021-12-14T14:23:36Z")

</div>

Hi,  
i have every 10-60 Minute Core dumps:

```
Dec 14 13:01:46 hostname systemd.sh[12345678]: /usr/local/WowzaStreamingEngine/bin/wms.sh: line 42: 786575 Aborted (core dumped) $_EXECJAVA $WMSTUNE_OPTS $JMXOPTIONS -Dcom.wowza.wms.runmode="service" -Dcom.wowza.wms.native.base="linux" -Dlog4j.configurationFile="$WMSCONFIG_HOME/conf/l>
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

```

and

Livestreaming will be aborted if not restart the WowzaStreamingEngine Service.

Wowza Version since yesterday is 4.8.16+1  
Linux CentOS 8  
Maybe we did not need to update the log4j patch?

Edit: I think we found out, that if customer connects his Encoder, then wowza engine crashes. But only today, before updates & applying fixes for log4j

---

<div class="post-metadata">

**Author:** ![Dan\_Donald](https://avatars.discourse-cdn.com/v4/letter/d/96bed5/32.png) [@Dan\_Donald](https://community.wowza.com/u/Dan_Donald)\
**Post date:** [January 6, 2022, 3:32pm UTC](https://community.wowza.com/t/wowza-core-dumped-after-changes-with-log4j/94321/2 "2022-01-06T15:32:33Z")

</div>

Servers/Service still crashing all the Time. Any Suggestions?