Unable to start/launch Jira 9.1.0 on port 8080

Question

localhost 8080 refused to connect after installation. below are the cmd logs.

C:\Program Files\Atlassian\Jira\bin>start-jira.bat

To run Jira in the foreground, start the server with start-jira.bat /fg

`sMMMMMMMMMMMMMM+
MMMMMMMMMMMMMM
:sdMMMMMMMMMMM
MMMMMM
`sMMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sMMMMMMMMMMM MMMMM
MMMMMM `UOJ
`sMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sdMMMMMMMMMM MMMMM
MMMMMM `UOJ
MMMMMM
+MMMMM
MMMMM
`UOJ

Atlassian Jira
Version : 9.1.0

JAVA_HOME "C:\Program Files\Java\jdk1.8.0_251" contains spaces. Please change to
a location without spaces if this causes problems.

If you encounter issues starting or stopping Jira, please see the Troubleshootin
g guide at https://docs.atlassian.com/jira/jadm-docs-091/Troubleshooting+install
ation

Using JIRA_HOME: C:\Program Files\Atlassian\Jira
Using CATALINA_BASE: "C:\Program Files\Atlassian\Jira"
Using CATALINA_HOME: "C:\Program Files\Atlassian\Jira"
Using CATALINA_TMPDIR: "C:\Program Files\Atlassian\Jira	emp"
Using JRE_HOME: "C:\Program Files\Atlassian\Jira\jre"
Using CLASSPATH: "C:\Program Files\Atlassian\Jira\bin\bootstrap.jar;C:\Pro
gram Files\Atlassian\Jira\bin	omcat-juli.jar"
Using CATALINA_OPTS: ""
'find' is not recognized as an internal or external command,
operable program or batch file.
'find' is not recognized as an internal or external command,
operable program or batch file.
'find' is not recognized as an internal or external command,
operable program or batch file.
'find' is not recognized as an internal or external command,
operable program or batch file.
****************************************************************************
******* Wrong JVM version! Jira requires 1.8 or 11 to run. *******
****************************************************************************
***
*** Output of java -version command is:
NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED -
-add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNN
AMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi
/sun.rmi.transport=ALL-UNNAMED
openjdk version "11.0.13" 2021-10-19
OpenJDK Runtime Environment Temurin-11.0.13+8 (build 11.0.13+8)
OpenJDK 64-Bit Server VM Temurin-11.0.13+8 (build 11.0.13+8, mixed mode)
*** (End of output) ***
***
*** If you want JIRA to start using this JVM
*** set environment variable 'ignore_jvm_version' to 'true'
***
****************************************************************************
C:\Program Files\Atlassian\Jira\bin>

tushar sangale · Answer

same problem I'm facing how to resolve issue .

Radek Dostál · Answer

What also strikes me as odd is this line

Using JRE_HOME: "C:\Program Files\Atlassian\Jira\jre\"

This should correspond to your JAVA_HOME (I think?).

Could you check in {jira_installation_directory}\bin\setenv.bat if there are specified JAVA_HOME and JRE_HOME variables? They might, or might not be, it's been a veery long time since I had my hands on a new installation.

In my case the first Jira instance I'm checking locally I see both variables on top of the file, and both point to the same directory.

Also found https://jira.atlassian.com/browse/JRASERVER-71475 which, albeit seems to be fixed in 8.18.1, seems to be related to what your Jira says about JRE_HOME.

Nic Brough -Adaptavist- · Answer

Ok, that one is worth trying, I'd expect a different error message, but if it's not worked, there's not much point looking at that.

Next thing is a look at the full environment.  You've reminded me that I've seen something like this a while ago, and it was a broken environment.

I rarely use windows (it's for the odd game, or downloading a real OS to replace it in my world), so I'm not sure this is the right command, but could you try, on the command line where you tried to start Jira, just a simple

set

and hit return.  This should give you a terminal full of environment variables, most of which will look wonderfully cryptic.  Some of them will be Java related, and what we're looking for is consistency.

For example, if $JAVA_HOME=C:\Java\Bobsjava, and $PATH=[stuff];C:\Java\Charliesjava\bin;[more stuff], then things are breaking because it's trying to use two different versions of Java!