It is simply a risk. It is not tested. Any functionality may fail eventually or have unknown side effects in the long run. It is also not clear to me why you want to update Java, but not Solr. If you want the latest security fixes, bug fixes and new features then I would go first for a new Solr version and afterwards for a newer JDK.
> Am 28.08.2019 um 21:58 schrieb Pushkar Raste <pushkar.ra...@gmail.com>: > > I understand that the problem will not be fixed. What I am trying to > understand is even with the exception (the only exception I saw after > running my Solr4 cluster on JDK11 for 4 weeks), I am able index and query > documents just fine. > > What does this exception really affect. > >> On Wed, Aug 28, 2019 at 3:08 PM Shawn Heisey <apa...@elyograg.org> wrote: >> >>> On 8/27/2019 8:22 AM, Pushkar Raste wrote: >>> I am trying to run Solr 4 on JDK11, although this version is not >> supported >>> on JDK11 it seems to be working fine except for the error/exception >> "Unmap >>> hack not supported on this platform". >>> What the risks/downsides of running into this. >> >> The first version of Solr that was qualified with Java 9 was Solr 7.0.0. >> New Java versions did not work properly with older versions of Solr. >> Java 8 is as high as you can go with Solr 4. >> >> Solr versions up through 4.7.x have a minimum Java version requirement >> of Java 6. From 4.8.0 through 5.x, Java 7 is required as a minimum. >> Starting with Solr 6.0.0, the minimum requirement moved to Java 8. When >> Solr 9.0.0 is released, its minimum requirement will be Java 11. >> >> Right now, with Solr 8.x being the current version, Solr 7.x is only >> going to get major bugfixes, and there will be no updates at all to >> version 6.x and older. The problem you're running into with Solr 4 on >> Java 11 will not be fixed. If you want to run Java 11, you will need to >> upgrade to the latest Solr 7.x or 8.x. Early 7.x versions would not >> work with Java 10 or later. >> >> Thanks, >> Shawn >> > -- > — Pushkar Raste
