ERR_CONNECTION_REFUSED
jdk=1.8
port=8082&8006,No port occupancy
service=tomcat&JIRASoftware131018202405 can start
In the tomcat's log folder I found a log: jirasoftware131018202405-stderr.2018-10-13.log,in this log ,i found some questions.
[main] org.apache.tomcat.util.scan.StandardJarScanner.processURLs Failed to scan [file:/C:/Program%20Files/Atlassian/JIRA/lib/commons-cli.jar] from classloader hierarchy
java.io.FileNotFoundException: C:\Program Files\Atlassian\JIRA\lib\commons-cli.jar
The system can not find the file specified:
-commons-cli.jar
-jts1_0.jar
-carol.jar
-jonas_timer.jar
-idb.jar
-classes12.jar
-p6psy.jar
This suggests a very broken installation, missing files, broken paths and so-on. I'd try re-installing.
sorry,That's not a problem with the installation package.I checked MD5.
I found that Tomcat9 I used is not supported.I switched to Tomcat 8.5.
There is no problem that the system cannot find the specified file after installation.
But I still can't use it. In the task manager I found that the service could not be started.
In the relevant log folder, I didn't find any useful information and no error message.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Java HotSpot(TM) 64-Bit Server VM (25.181-b13) for windows-amd64 JRE (1.8.0_181-b13), built on Jul 7 2018 04:01:33 by "java_re" with MS VC++ 10.0 (VS2010)
Memory: 4k page, physical 25103064k(14024668k free), swap 26675928k(8611240k free)
CommandLine flags: -XX:GCLogFileSize=20971520 -XX:InitialHeapSize=268435456 -XX:MaxHeapSize=805306368 -XX:NumberOfGCLogFiles=5 -XX:-OmitStackTraceInFastThrow -XX:+PrintGC -XX:+PrintGCCause -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseGCLogFileRotation -XX:-UseLargePagesIndividualAllocation -XX:+UseParallelGC
Heap
PSYoungGen total 76288K, used 10486K [0x00000000f0000000, 0x00000000f5500000, 0x0000000100000000)
eden space 65536K, 16% used [0x00000000f0000000,0x00000000f0a3d940,0x00000000f4000000)
from space 10752K, 0% used [0x00000000f4a80000,0x00000000f4a80000,0x00000000f5500000)
to space 10752K, 0% used [0x00000000f4000000,0x00000000f4000000,0x00000000f4a80000)
ParOldGen total 175104K, used 0K [0x00000000d0000000, 0x00000000dab00000, 0x00000000f0000000)
object space 175104K, 0% used [0x00000000d0000000,0x00000000d0000000,0x00000000dab00000)
Metaspace used 4776K, capacity 5100K, committed 5248K, reserved 1056768K
class space used 533K, capacity 604K, committed 640K, reserved 1048576K
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh, so many things are wrong here.
>sorry,That's not a problem with the installation package.I checked MD5.
Not what I said. I said you have a broken installation. The stuff that is there after you install is wrong
>I found that Tomcat9 I used is not supported.I switched to Tomcat 8.5.
This suggests what the problem really is. It sounds like you are botching the installation by trying to take a properly installed Jira and wedging it into your own installation of Tomcat. While that is possible, it's not necessary and gives you lots of ways of getting it completely wrong, which it sounds like you have.
Could you run the installer properly and retry this with a clean simple installation without trying to jam it into your own Tomcat install?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, I am not very good at English, I think the communication between us may be a bit problematic.
I removed some software that might affect Jira and then used the default installation, but still can't open jira's service.
I checked the port and firewall, no problem.
Now I can't find where there might be a problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The main error you are getting is because the installation is damaged. There are missing files, or the startup environment files have been damaged and are not setting the paths correctly.
I don't think you can do much other than start again, with a clean installation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.