JAVAPRO<p>Think <a href="https://mastodon.social/tags/Log4Shell" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Log4Shell</span></a> was a one-off bug? Think again.. What really caused it? How close was <a href="https://mastodon.social/tags/Log4j" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Log4j</span></a> to dying — multiple times? And what’s next for one of <a href="https://mastodon.social/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Java</span></a>’s oldest libraries? Christian Grobmeier’s new piece will surprise you.</p><p>Dive in: <a href="https://javapro.io/2025/06/10/the-long-history-of-log4j/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">javapro.io/2025/06/10/the-long</span><span class="invisible">-history-of-log4j/</span></a></p><p><a href="https://mastodon.social/tags/JVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JVM</span></a> <a href="https://mastodon.social/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Java</span></a> <span class="h-card" translate="no"><a href="https://mastodon.social/@theasf" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>theasf</span></a></span></p>