The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Java Virtual Machine refers to wrong JVM.dll after upgrade

Cow Hills
August 10, 2018

Hello,

I have upgraded my JIRA Service Desk application to the 3.14.2 x64 version.
After this upgrade to service wouldn't start anymore.

The problem was that in tomcat8w.exe //ES//JIRAServiceDesk030718143054 the Java Vritual Machine was referring to C:\Program Files\Java\jre-10.0.2\bin\server\jvm.dll. with that dll the application could not start because some of the Java Options like PrintGCDetails are not supported.

when i changed the Java Virtual Machine back to C:\Program Files\Atlassian\JIRA\jre\bin\server\jvm.dll all the problems where gone.

I think this is a bug or am i doing something wrong?

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Andy Heinzer
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 10, 2018

Jira does not yet have support for Java 10.  Please see the Supported Platforms documentation.  You will see that currently, Jira only supports the Oracle JRE/JDK of the 1.8.x versions (aka Java 8).

If you have set your $JAVA_HOME variable to this other installation path with a Java 10 jre, Jira might not behave as expected.   Since these Windows exe installations can also bundle Java 8 jre with them, that could explain why this works with the old path but not your current path.   I would recommend setting your javahome to use a Java 8 installation path and restart Jira to make sure that you are using a supported platform.

TAGS
AUG Leaders

Atlassian Community Events