Advisory regarding running Omniscope as a Windows Service

Only relevant for existing installation of Omniscope which are running as Windows service. If you install Omniscope on a fresh machine using build 21054 or later you do not need worry, as these changes are now part of the default wrapper.conf which is bundled with the installer.

If you are running Omniscope as a Windows service you would need to make sure your wrapper.conf located inside the service folder in the installation directory is updated to ensure it has the following setting. 

1. Stop the Omniscope windows service from Services application on your Windows machine.
   
   
2. Open the wrapper.conf in notepad.
   
   
3. Edit the wrapper.java.additional properties to include the following.
   
   NOTE: The properties have a number which is incremented for each new property i.e. if you already have wrapper.java.additional.1 then the next one will be wrapper.java.additional.2
   
   New property that needs to be added:
   
   wrapper.java.additional.2=-Djava.awt.headless=true
   
   
4. Save the wrapper.conf.
   
   
5. Restart the Windows service.
   
   

If you are using a build later than 2020.4 b21046 you would need to also add the following additional properties:

wrapper.java.additional.1=-XX:+UseG1GC

wrapper.java.additional.2=-Djava.awt.headless=true

wrapper.java.additional.3=-Djava.locale.providers=COMPAT,CLDR,SPI

wrapper.java.additional.4=--add-opens=java.desktop/java.awt=ALL-UNNAMED

wrapper.java.additional.5=--add-opens=java.desktop/javax.swing=ALL-UNNAMED

wrapper.java.additional.6=--add-opens=java.desktop/sun.swing=ALL-UNNAMED

wrapper.java.additional.7=--add-opens=java.base/java.io=ALL-UNNAMED

wrapper.java.additional.8=--add-opens=java.desktop/com.sun.swing.plaf.windows=ALL-UNNAMED

wrapper.java.additional.9=--illegal-access=permit

0 Votes