So we've got a fresh install of JIRA that we're trying to setup. However, when we run the service, it does say "started", but we can't connect to the server (eventual timeout). The service also won't properly stop at that point.
We tried starting manually via the startup_bundled_jre.bat script, and this was the only output for a good twenty minutes:
Jun 17, 2013 3:07:19 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: c:\Program Files\Atlassian\JIRA\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit\;C:\Program Files (x86)\Panda Security\WaAgent\Common;C:\Program Files (x86)\Git\cmd;C:\Program Files (x86)\Git\bin;.
Jun 17, 2013 3:07:20 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8090"]
Jun 17, 2013 3:07:20 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 660 ms
Jun 17, 2013 3:07:20 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Jun 17, 2013 3:07:20 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.29
Any idea what might be going on here? We had an instance running previously but we're now setting up a production server instance - we haven't even migrated any data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.