On 12/9/22 12:43, Shawn Heisey wrote:
If it doesn't, it's most likely a bug in Java.
This part of what I wrote is a little too broad.
There could be a bug in the Apache software, but if that's the case,
you'll usually find something on the project's NEWS page about a MAJOR
bug that affects everyone, with a recommendation to upgrade ASAP. Such
things are very uncommon, but not impossible. When it happens, it is
usually found and fixed VERY quickly.
In the absence of an announcement from the project about a major bug in
that software component, the problem is usually in Java, the OS, or the
hardware. On the Apache Solr project, we recently encountered a bug in
Java 17 affecting one of Solr's dependencies that could cause Solr to
crash. A workaround for that bug was found and it was announced by the
project. The next version of Solr included that workaround.
https://solr.apache.org/news.html#java-17-bug-affecting-solr
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
