9.6 Upgrade - Sonar.web not starting without wrapper.conf

I’m trying to upgrade SonarQube from 9.4 to 9.6. I noticed wrapper.conf is no longer being used.
When trying the steps described in documentation to install the service on Windows, I’m currently unable to get the sonar.web correctly started.

In logs no sonar.web is created, I’m only seeing a warning in sonar.log:
All other log files (es.log, SonarServiceWrapper.wrapper.log) show INFO / DEBUG messages.

WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [Web Server]: 1

In Windows Application Event Logs I’m seeing following warning being logged as well:

Child process [7800 - java.exe -Xms8m -Xmx32m -Djava.awt.headless=true --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.management/sun.management=ALL-UNNAMED --add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED -cp “…....\lib\sonar-application-” “org.sonar.application.App” ] finished with 0

Has anybody come across these difficulties before, is there no way to (still) use the wrapper.conf file as it never failed me before …


Are you using 9.6 or 9.6.1? We issued a patch for a problem starting up on Windows…


Hi Ann,

Thank you for looking into this. I’m trying to upgrade from towards, so the latest version I can find.

Tried following actions as well: Reinstalling service as Administrator => no impact

Also noticed the comment in /bin/windows-x86-64/lib/find_java.bat to install a environmental variable SONAR_JAVA_PATH with the right location to the java.exe, but it’s of no use either.

Sharing the current wrapper.conf file of our 9.4 configuration with different lines in comparison with the default one provided during download, maybe you notice something odd, there is only a small difference at beginning & end of the file:

Hello @gCassy,

Thanks for all the information you provided.
After 9.6.1, we included 2 more fixes in the Windows scripts in 9.7, that might address your issue.

If you can’t update to 9.7, you could try to view and copy the changes that we did directly to the scripts of 9.6.1 and try to run it again:


1 Like