7.4: Solr/Jetty failure with current Java versions

cancel
Showing results for 
Search instead for 
Did you mean: 
atTheBeach
Active Member II

7.4: Solr/Jetty failure with current Java versions

Jump to solution

This is an old one, but it seems to be back, and the old answers/bug fixes don't seem to relevant. Solr produces this error message:

Invalid Java version 17.0.8.1

I have two Community 7.4 test systems running 17.0.8.1, and one works, but the other doesn't:

  1. Works: Zulu 17.0.8.1, alfresco-search-services-2.0.1.zip
  2. Doesn't work: Ubuntu-installed OpenJDK 17 ('apt install openjdk-17-jdk-headless'), 17.0.8.1, alfresco-search-services-2.0.8.1.zip

It's going to take some hours to find out what's going on here, so I thought I'd check in first: anyone seen this? Any ideas?

 

1 Solution

Accepted Solutions
atTheBeach
Active Member II

Re: 7.4: Solr/Jetty failure with current Java versions

Jump to solution

The original Jetty bug report from Jan 2018 was fixed in Jetty 9.4, but it turns out that alfresco-search-services.zip is still on 9.3 (Jetty is now v12). This bug was that Jetty wouldn't work with a Java installation which had a 4-part version number (ie. 17.0.8.1). However, it's not as simple as that, as 17.0.8.1 can be made to work in some circumstances.

Anyway, fixed by installing Temurin 17:

$ /opt/jdk-17.0.9+9/bin/java -version
openjdk version "17.0.9" 2023-10-17
OpenJDK Runtime Environment Temurin-17.0.9+9 (build 17.0.9+9)
OpenJDK 64-Bit Server VM Temurin-17.0.9+9 (build 17.0.9+9, mixed mode, sharing)

View solution in original post

1 Reply
atTheBeach
Active Member II

Re: 7.4: Solr/Jetty failure with current Java versions

Jump to solution

The original Jetty bug report from Jan 2018 was fixed in Jetty 9.4, but it turns out that alfresco-search-services.zip is still on 9.3 (Jetty is now v12). This bug was that Jetty wouldn't work with a Java installation which had a 4-part version number (ie. 17.0.8.1). However, it's not as simple as that, as 17.0.8.1 can be made to work in some circumstances.

Anyway, fixed by installing Temurin 17:

$ /opt/jdk-17.0.9+9/bin/java -version
openjdk version "17.0.9" 2023-10-17
OpenJDK Runtime Environment Temurin-17.0.9+9 (build 17.0.9+9)
OpenJDK 64-Bit Server VM Temurin-17.0.9+9 (build 17.0.9+9, mixed mode, sharing)