Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unable to install 2 JIRA instance on same machine/server

Hello Team,

We are trying to install two instance on same machine/server but unable to install.

We have tried the following steps:

1. Install 1st JIRA instance successfully with port 8080 & 8005 on D drive

2. Installed 2nd JIRA instance with port 8090 & 8015 on E drive but after installing we faced the following issues;

a) JIRAHOME directory is not created

b) JIRA service is not created for 2nd Instance.

c) Try to set JAVA_HOME in environment variable for 2nd JIRA instance then is is pointing to JAVA_HOME variable which was created for 1st JIRA instance. Hence, unable to set JAVA_HOME for JIRA 2nd instance

 

Could you please help us how to create  two JIRA instance on same machine?

Please send us the proper step for solving this issue.

 

Thanks & Regards,

Dnyaneshwar

7 answers

0 votes
miikhy Community Leader Jul 06, 2018

Hey Dnyaneshwar,

Here is the official KB about this: https://confluence.atlassian.com/jira/running-multiple-instances-of-jira-on-one-machine-222200571.html

Two windows services shouldn't be a problem apparently. How have you made sure JIRA_HOME is independant from first one?

Also, I would recommend not to use 8090 as it's default for Confluence, just a best practice thing without impact :)

Cheers

Hi Micky - in my case, i have JRE installed in "C:\Program Files (x86)\Java\jre1.8.0_161".  My Environment (Sytem) Variable = C:\Progra~2\Java\jre1.8.0_161.

I am using Windows Server 2016 (64-bit).  And yes they have different JIRA_HOME, Database, Listening and Shutdown Ports.

As I mentioned in my comment here earlier, the 2nd JIRA instance would run if I start the "start-jira.bat" file.  To me that means the entire JIRA installation completed successfully.  Also, the JIRA Service would be installed and appear in "Services".  The problem is the service won't start.

What could I be missing here?

Thanks,

Hello Micky,

Thanks for the update.

We have gone through above shared link with us.

  • Could you please elaborate below statement from above shared link? we are unable to understand

           a) When using services within windows, using 2 different windows service definitions

           b) Not deploying multiple instances using a Single Tomcat Application Container.

As per your recommendation, we tried with another listening port like 8081 & shutdown port 8006.Please correct me if we are using wrong port?

We are facing the same following problem after installing 2nd instance;

1) "JIRAHOME" directory is created but there is no any folders are created within that directory [like import,export,data,log,temp,cache,monitor and analytics_log]

2) JIRA service [Windows service] is not created for 2nd Instance.

3) Try to set JAVA_HOME in environment variable for 2nd JIRA instance then is is pointing to JAVA_HOME variable which was created for 1st JIRA instance. Hence, unable to set JAVA_HOME for JIRA 2nd instance

Please send me the steps in detail for two instance creation on same machine?

 

Thanks & Regards,

Dnyaneshwar

  

Hi,

If the first instance work fine as service , so try to install the second as not a service in wizard and after installed it, try to create service with different name for the second instance.

Thanks Nadir,

We did the 2nd installation as suggested by you and it is working fine.

Can you please help us and provide details about how to create service for the second instance, which is installed not as a service?

I am running into the same exact problem.  The first JIRA instance is running perfectly.  The 2nd instance runs only when i start the "start-jira.bat" file.  When I try to install it as a Service, I get the same error as Dnyaneshwar.

"The JIRASoftware service terminated with the following service-specific error: Incorrect function."


Help would be much appreciated.

Thanks.

Any help please from our Community on this issue?

Mentioning here the experts@Nic Brough _Adaptavist_@miikhy.

Thank you.

miikhy Community Leader Jul 31, 2018

Hey there!

Have you tried the above suggestion from @ridan about the KB?(manual service install: https://confluence.atlassian.com/adminjiraserver071/running-jira-applications-as-a-windows-service-802593173.html?_ga=2.207247379.125991066.1532994752-1581768906.1525278748)

I imagine that two services might be in conflict on windows if they both use the same config, manual should solve it.

Have you also checked both services are reaching different targets in the Service admin page of your windows machine?

I unfortunately use unix based systems most of the time or tar.gz releases but hope I can help!

Let us know!

Cheers

Hi @miikhy- i did before and did it again after deleting the service.  Here are the screenshots:

JIRAServiceInstall_Manual.PNG

After successfully installing the service and setting it to auto-start.  I rebooted the server (Windows 2016).

However, I found the service is still in Stopped mode so I tried to start it, but got the error below (same error I have been having since day 1):

JIRAServiceInstall_Manual2.PNG

I thought maybe the reason for this error is that when I installed this 2nd JIRA instance, I installed it as a service.  I am now inclined to uninstall it and re-install, but this time not as a service so I can set the service manually.

Thoughts, please?

Thanks!

miikhy Community Leader Aug 02, 2018

Hi Deney,

Could you have a look at/share the catalina.out and atlassian-jira.log ?

That should give more details :( to be honest I’m running out of ideas, that could give more perspectives!

Thanks

Thanks @miikhy.  Here below is the catalina.out log.  I appreciate the assistance.

Regards,

++++catalina.out == START++++

02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.6
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Oct 6 2016 20:15:31 UTC
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.6.0
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows Server 2016
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 10.0
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: x86
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:\Progra~2\Java\jre1.8.0_161
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_161-b12
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\Program Files\AtlassianJIRATest\JIRA
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\Program Files\AtlassianJIRATest\JIRA
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms384m
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx768m
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
02-Aug-2018 00:03:20.411 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-OmitStackTraceInFastThrow
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.plugins.startup.options=
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\Program Files\AtlassianJIRATest\JIRA\conf\logging.properties
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xloggc:C:\Program Files\AtlassianJIRATest\JIRA\bin\..\logs\atlassian-jira-gc-%t.log
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseGCLogFileRotation
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:NumberOfGCLogFiles=5
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:GCLogFileSize=20M
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDetails
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCTimeStamps
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCCause
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Program Files\AtlassianJIRATest\JIRA
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\Program Files\AtlassianJIRATest\JIRA
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\Program Files\AtlassianJIRATest\JIRA\temp
02-Aug-2018 00:03:20.426 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Progra~2\Java\jre1.8.0_161\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\Users\DPerea\AppData\Local\Microsoft\WindowsApps;;.
02-Aug-2018 00:03:20.551 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8090"]
02-Aug-2018 00:03:20.567 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 494 ms
02-Aug-2018 00:03:20.583 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina
02-Aug-2018 00:03:20.583 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.6
02-Aug-2018 00:03:29.537 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler [http-nio-8090]
02-Aug-2018 00:03:29.553 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
02-Aug-2018 00:03:29.553 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 8990 ms
02-Aug-2018 00:05:37.258 WARNING [http-nio-8090-exec-2] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://xxx.xx.xx.xx:xxxx/rest/activity-stream/1.0/preferences?_=1533182737520, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.6
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Oct 6 2016 20:15:31 UTC
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.6.0
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows Server 2016
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 10.0
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: x86
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:\Progra~2\Java\jre1.8.0_161
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_161-b12
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\Program Files\AtlassianJIRATest\JIRA
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\Program Files\AtlassianJIRATest\JIRA
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms384m
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx768m
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-OmitStackTraceInFastThrow
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.plugins.startup.options=
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\Program Files\AtlassianJIRATest\JIRA\conf\logging.properties
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xloggc:C:\Program Files\AtlassianJIRATest\JIRA\bin\..\logs\atlassian-jira-gc-%t.log
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseGCLogFileRotation
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:NumberOfGCLogFiles=5
02-Aug-2018 00:36:38.502 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:GCLogFileSize=20M
02-Aug-2018 00:36:38.517 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDetails
02-Aug-2018 00:36:38.517 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
02-Aug-2018 00:36:38.517 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCTimeStamps
02-Aug-2018 00:36:38.517 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCCause
02-Aug-2018 00:36:38.517 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Program Files\AtlassianJIRATest\JIRA
02-Aug-2018 00:36:38.517 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\Program Files\AtlassianJIRATest\JIRA
02-Aug-2018 00:36:38.517 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\Program Files\AtlassianJIRATest\JIRA\temp
02-Aug-2018 00:36:38.517 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Progra~2\Java\jre1.8.0_161\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\Users\DPerea\AppData\Local\Microsoft\WindowsApps;;.
02-Aug-2018 00:36:38.689 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8090"]
02-Aug-2018 00:36:38.705 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 605 ms
02-Aug-2018 00:36:38.720 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina
02-Aug-2018 00:36:38.720 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.6
02-Aug-2018 00:36:50.019 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler [http-nio-8090]
02-Aug-2018 00:36:50.034 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
02-Aug-2018 00:36:50.034 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 11334 ms
02-Aug-2018 00:38:45.499 WARNING [http-nio-8090-exec-6] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://xxx.xx.xx.xx:xxxx/rest/activity-stream/1.0/preferences?_=1533184722581, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

++++catalina.out == END+++++

+++atlassian-jira.log == START +++

2018-08-02 00:36:49,613 localhost-startStop-1 INFO [c.a.jira.startup.JiraHomeStartupCheck] The jira.home directory 'F:\JIRA-TEST Data\JIRAHOME' is validated and locked for exclusive use by this instance.
2018-08-02 00:36:49,753 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

****************
JIRA starting...
****************

2018-08-02 00:36:50,050 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

___ Environment _____________________________

JIRA Build : 7.7.0#77001-sha1:3be31511dfd860a9aedae108fbd5f079b4968c6a
Build Date : Thu Jan 11 00:00:00 EST 2018
JIRA Installation Type : Standalone
Application Server : Apache Tomcat/8.5.6 - Servlet API 3.1
Java Version : 1.8.0_161 - Oracle Corporation
Current Working Directory : C:\Program Files\AtlassianJIRATest\JIRA\bin
Maximum Allowable Memory : 742MB
Total Memory : 371MB
Free Memory : 271MB
Used Memory : 100MB
Memory Pool: Code Cache : Code Cache: init = 163840(160K) used = 3290880(3213K) committed = 3309568(3232K) max = 33554432(32768K)
Memory Pool: Metaspace : Metaspace: init = 0(0K) used = 13256712(12946K) committed = 13631488(13312K) max = -1(-1K)
Memory Pool: Eden Space : Eden Space: init = 107479040(104960K) used = 79942760(78069K) committed = 107544576(105024K) max = 214827008(209792K)
Memory Pool: Survivor Space : Survivor Space: init = 13369344(13056K) used = 0(0K) committed = 13369344(13056K) max = 26804224(26176K)
Memory Pool: Tenured Gen : Tenured Gen: init = 268435456(262144K) used = 26572656(25949K) committed = 268435456(262144K) max = 536870912(524288K)
JVM Input Arguments : -Xms384m -Xmx768m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:-OmitStackTraceInFastThrow -Datlassian.plugins.startup.options= -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Djava.util.logging.config.file=C:\Program Files\AtlassianJIRATest\JIRA\conf\logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xloggc:C:\Program Files\AtlassianJIRATest\JIRA\bin\..\logs\atlassian-jira-gc-%t.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=20M -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintGCCause -Dcatalina.base=C:\Program Files\AtlassianJIRATest\JIRA -Dcatalina.home=C:\Program Files\AtlassianJIRATest\JIRA -Djava.io.tmpdir=C:\Program Files\AtlassianJIRATest\JIRA\temp
Java Compatibility Information : JIRA version = 7.7.0, Java Version = 1.8.0_161

___ Java System Properties ________________

atlassian.plugins.startup.options :
atlassian.standalone : JIRA
awt.toolkit : sun.awt.windows.WToolkit
catalina.base : C:\Program Files\AtlassianJIRATest\JIRA
catalina.home : C:\Program Files\AtlassianJIRATest\JIRA
catalina.useNaming : true
common.loader : "${catalina.base}/lib",
"${catalina.base}/lib/*.jar",
"${catalina.home}/lib",
"${catalina.home}/lib/*.jar"
file.encoding : Cp1252
file.encoding.pkg : sun.io
java.awt.graphicsenv : sun.awt.Win32GraphicsEnvironment
java.awt.headless : true
java.awt.printerjob : sun.awt.windows.WPrinterJob
java.class.version : 52.0
java.home : C:\Progra~2\Java\jre1.8.0_161
java.io.tmpdir : C:\Program Files\AtlassianJIRATest\JIRA\temp
java.naming.factory.initial : org.apache.naming.java.javaURLContextFactory
java.naming.factory.url.pkgs : org.apache.naming
java.protocol.handler.pkgs : org.apache.catalina.webresources
java.runtime.name : Java(TM) SE Runtime Environment
java.runtime.version : 1.8.0_161-b12
java.specification.name : Java Platform API Specification
java.specification.vendor : Oracle Corporation
java.specification.version : 1.8
java.util.logging.config.file : C:\Program Files\AtlassianJIRATest\JIRA\conf\logging.properties
java.util.logging.manager : org.apache.juli.ClassLoaderLogManager
java.vendor : Oracle Corporation
java.vendor.url : http://java.oracle.com/
java.vendor.url.bug : http://bugreport.sun.com/bugreport/
java.version : 1.8.0_161
java.vm.info : mixed mode
java.vm.name : Java HotSpot(TM) Client VM
java.vm.specification.name : Java Virtual Machine Specification
java.vm.specification.vendor : Oracle Corporation
java.vm.specification.version : 1.8
java.vm.vendor : Oracle Corporation
java.vm.version : 25.161-b12
jdk.tls.ephemeralDHKeySize : 2048
mail.mime.decodeparameters : true
org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER : true
org.dom4j.factory : com.atlassian.core.xml.InterningDocumentFactory
os.arch : x86
os.name : Windows Server 2016
os.version : 10.0
package.access : sun.,
org.apache.catalina.,
org.apache.coyote.,
org.apache.jasper.,
org.apache.tomcat.
package.definition : sun.,
java.,
org.apache.catalina.,
org.apache.coyote.,
org.apache.jasper.,
org.apache.naming.,
org.apache.tomcat.
server.loader :
shared.loader :
sun.arch.data.model : 32
sun.boot.library.path : C:\Progra~2\Java\jre1.8.0_161\bin
sun.cpu.endian : little
sun.cpu.isalist : pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
sun.desktop : windows
sun.io.unicode.encoding : UnicodeLittle
sun.java.command : org.apache.catalina.startup.Bootstrap start
sun.java.launcher : SUN_STANDARD
sun.jnu.encoding : Cp1252
sun.management.compiler : HotSpot Client Compiler
sun.os.patch.level :
sun.stderr.encoding : cp437
sun.stdout.encoding : cp437
tomcat.util.buf.StringCache.byte.enabled : true
tomcat.util.scan.StandardJarScanFilter.jarsToScan : log4j-web*.jar,
log4j-taglib*.jar,
log4javascript*.jar,
slf4j-taglib*.jar
tomcat.util.scan.StandardJarScanFilter.jarsToSkip : bootstrap.jar,
commons-daemon.jar,
tomcat-juli.jar,
annotations-api.jar,
el-api.jar,
jsp-api.jar,
servlet-api.jar,
websocket-api.jar,
jaspic-api.jar,
catalina.jar,
catalina-ant.jar,
catalina-ha.jar,
catalina-storeconfig.jar,
catalina-tribes.jar,
jasper.jar,
jasper-el.jar,
ecj-*.jar,
tomcat-api.jar,
tomcat-util.jar,
tomcat-util-scan.jar,
tomcat-coyote.jar,
tomcat-dbcp.jar,
tomcat-jni.jar,
tomcat-websocket.jar,
tomcat-i18n-en.jar,
tomcat-i18n-es.jar,
tomcat-i18n-fr.jar,
tomcat-i18n-ja.jar,
tomcat-juli-adapters.jar,
catalina-jmx-remote.jar,
catalina-ws.jar,
tomcat-jdbc.jar,
tools.jar,
commons-beanutils*.jar,
commons-codec*.jar,
commons-collections*.jar,
commons-dbcp*.jar,
commons-digester*.jar,
commons-fileupload*.jar,
commons-httpclient*.jar,
commons-io*.jar,
commons-lang*.jar,
commons-logging*.jar,
commons-math*.jar,
commons-pool*.jar,
jstl.jar,
taglibs-standard-spec-*.jar,
geronimo-spec-jaxrpc*.jar,
wsdl4j*.jar,
ant.jar,
ant-junit*.jar,
aspectj*.jar,
jmx.jar,
h2*.jar,
hibernate*.jar,
httpclient*.jar,
jmx-tools.jar,
jta*.jar,
log4j*.jar,
mail*.jar,
slf4j*.jar,
xercesImpl.jar,
xmlParserAPIs.jar,
xml-apis.jar,
junit.jar,
junit-*.jar,
hamcrest-*.jar,
easymock-*.jar,
cglib-*.jar,
objenesis-*.jar,
ant-launcher.jar,
cobertura-*.jar,
asm-*.jar,
dom4j-*.jar,
icu4j-*.jar,
jaxen-*.jar,
jdom-*.jar,
jetty-*.jar,
oro-*.jar,
servlet-api-*.jar,
tagsoup-*.jar,
xmlParserAPIs-*.jar,
xom-*.jar
user.country : US
user.dir : C:\Program Files\AtlassianJIRATest\JIRA\bin
user.home : C:\Users\ADMINNAME
user.language : en
user.name : ADMINNAME
user.script :
user.timezone : America/New_York
user.variant :

Do you need the rest of the atlassian-jira.log file?  It is quite long and the Text Editor is complaining that I should post it as Plain Text.  I think what it "actually" wants to say is that it cannot accommodate long posts.  :)

Thanks again @miikhy

miikhy Community Leader Aug 03, 2018

Hi,

The logs you posted seems to be OK. Have you tried the manual install with a different name that "JIRA"? such as 

service.bat install JIRA2

That should help? I've just figured you used the default name which might conflict with second service...

Could you also upload the logs (full version) somewhere wo that we could try and search deeper..

Have you also tried contacting Atlassian support directly?

Thanks

Hi,

I never tried it , could you try this

service.bat install JIRA2 

I needed to change the value of the DISPLAYNAME variable in service.bat in order to be able to install the windows service of my second Jira instance.  The display name seems to need to be different for each service instance.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

271 views 16 17
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you