Issue Summary

Starting Jira 8 on Windows with AdoptOpenJDK 11.0.4_11 causes an exception

Environment

• Jira 8.4.2
• Service Desk 4.4.2
• Portfolio 3.12.0
• Windows Server 2019
• AdoptOpenJDK 11.0.4_11

Steps to Reproduce

1. Unpack JDK and configure JAVA_HOME and PATH
2. Configure and start Jira as a service (from zip distribution)
3. Start service

Expected Results

• Jira starts

Actual Results

• Error page
  The below exception is thrown in the attlassian-jira.log file:

  .2019-10-17 03:06:55,529 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
  2019-10-17 03:06:55,529 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.
  2019-10-17 03:06:55,576 JIRA-Bootstrap ERROR      [c.a.jira.startup.LauncherContextListener] Unable to start JIRA.
  java.lang.UnsatisfiedLinkError: C:\Java\adopt\jdk-11.0.4+11\bin\awt.dll: Can't find dependent libraries
  	at java.base/java.lang.ClassLoader$NativeLibrary.load0(Native Method)
  	at java.base/java.lang.ClassLoader$NativeLibrary.load(ClassLoader.java:2430)
  	at java.base/java.lang.ClassLoader$NativeLibrary.loadLibrary(ClassLoader.java:2487)
  	at java.base/java.lang.ClassLoader.loadLibrary0(ClassLoader.java:2684)
  	at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2638)
  	at java.base/java.lang.Runtime.loadLibrary0(Runtime.java:829)
  	at java.base/java.lang.System.loadLibrary(System.java:1867)
  	at java.desktop/java.awt.Toolkit$3.run(Toolkit.java:1395)
  	at java.desktop/java.awt.Toolkit$3.run(Toolkit.java:1393)
  	at java.base/java.security.AccessController.doPrivileged(Native Method)
  	at java.desktop/java.awt.Toolkit.loadLibraries(Toolkit.java:1392)
  	at java.desktop/java.awt.Toolkit.<clinit>(Toolkit.java:1425)
  	at java.desktop/sun.awt.AppContext$2.run(AppContext.java:282)
  	at java.desktop/sun.awt.AppContext$2.run(AppContext.java:271)
  	at java.base/java.security.AccessController.doPrivileged(Native Method)
  	at java.desktop/sun.awt.AppContext.initMainAppContext(AppContext.java:271)
  	at java.desktop/sun.awt.AppContext$3.run(AppContext.java:326)
  	at java.desktop/sun.awt.AppContext$3.run(AppContext.java:309)
  	at java.base/java.security.AccessController.doPrivileged(Native Method)
  	at java.desktop/sun.awt.AppContext.getAppContext(AppContext.java:308)
  	at java.desktop/javax.imageio.spi.IIORegistry.getDefaultInstance(IIORegistry.java:129)
  	at java.desktop/javax.imageio.ImageIO.<clinit>(ImageIO.java:66)
  	at com.atlassian.jira.startup.ImageIOProviderScannerLauncher.start(ImageIOProviderScannerLauncher.java:14)
  	at com.atlassian.jira.startup.DefaultJiraLauncher.preDbLaunch(DefaultJiraLauncher.java:120)
  	at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:103)
  	at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
  	at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:102)
  	at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
  	at java.base/java.lang.Thread.run(Thread.java:834)
  
  

Workaround

There are two workarounds for this issue. One is to use AdoptOpenJDK 11.0.1_13 which doesn't have this issue.

The other one requires some additional work:
1. Stop Jira service
2. Change the permissions for JVM dir (and subdirs), add 'Local Account' (make sure it's added to all files and subdirectories)
3. Modify jira_install_dir/bin/serivce.bat (at the end of the script)
Change

--StartMode jvm ^
--StopMode jvm ^
into

--StartMode java ^
--StopMode java ^
4. Reinstall the service (in the jira_install_dir/bin directory run `service remove` and `service install`
5. Run Jira service again