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: 

set environment variable 'ignore_jvm_version' to 'true'

roopesh
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 18, 2021

HI ALl , 

i am getting following error

please help me

 

If you want JIRA to start using this JVM
*** set environment variable 'ignore_jvm_version' to 'true'

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
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.
March 18, 2021

In almost all cases, it will be better for you to use a supported Java version, not override the check - Jira does not work well with unsupported Java versions.

Muhammad Akram Sharifi
Contributor
August 4, 2021

this is not about support or unsupported versions. 

Nic Brough -Adaptavist-
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 4, 2021

It very much is about supported versions, the warning you are getting is about you trying to use the wrong version of Java (i.e. the unsupported version)

My strong recommendation is that you use a supported version of Java.

If you want to persist with an unsupported version, then 

  • Change the flag the warning is about
  • Expect things to go wrong,
  • Don't bother doing anything serious for production with it, as you'll need to retest and re-do it all on a supported JVM before it goes to production