Fresh install of JIRA fails to startup

Steps:

- Download latest version of JIRA for Windows 7 (64 bit installer)

- Install JIRA to run as standalone (not as a service)

- Execute startup_bundled_jre.bat from command window

- Java starts and eventually shuts down

See attached log entries below:

--

15-May-2012 9:09:55 AM org.apache.catalina.core.StandardServer await

SEVERE: StandardServer.await: create 8005 :

java.net.BindException: Cannot assign requested address: JVM_Bind

at java.net.PlainSocketImpl.socketBind(Native Method)

at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)

at java.net.ServerSocket.bind(ServerSocket.java:328)

at java.net.ServerSocket.<init>(ServerSocket.java:194)

at org.apache.catalina.core.StandardServer.await(StandardServer.java:406)

at org.apache.catalina.startup.Catalina.await(Catalina.java:676)

at org.apache.catalina.startup.Catalina.start(Catalina.java:628)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

15-May-2012 9:09:56 AM org.apache.coyote.http11.Http11Protocol pause

INFO: Pausing Coyote HTTP/1.1 on http-8080

15-May-2012 9:09:57 AM org.apache.catalina.core.StandardService stop

INFO: Stopping service Catalina

15-May-2012 9:09:57 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Spring executor 1 but has failed to stop it. This is very likely to create a memory leak.

15-May-2012 9:09:57 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Spring executor 2 but has failed to stop it. This is very likely to create a memory leak.

15-May-2012 9:09:57 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Spring executor 3 but has failed to stop it. This is very likely to create a memory leak.

15-May-2012 9:09:57 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Spring executor 4 but has failed to stop it. This is very likely to create a memory leak.

15-May-2012 9:09:57 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Spring executor 5 but has failed to stop it. This is very likely to create a memory leak.

15-May-2012 9:09:57 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Spring executor 6 but has failed to stop it. This is very likely to create a memory leak.

15-May-2012 9:09:57 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Spring executor 7 but has failed to stop it. This is very likely to create a memory leak.

15-May-2012 9:09:57 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application created a ThreadLocal with key of type java.lang.ThreadLocal (value java.lang.ThreadLocal@11ba1db5 ) and a value of type org.dom4j.DocumentFactory (value org.dom4j.DocumentFactory@51f45f2a ) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

15-May-2012 9:09:57 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application created a ThreadLocal with key of type com.google.inject.internal.InjectorImpl$1 (value com.google.inject.internal.InjectorImpl$1@3c80d0bb ) and a value of type java.lang.Object (value Ljava.lang.Object;@2d07c405 ) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

15-May-2012 9:09:57 AM org.apache.coyote.http11.Http11Protocol destroy

INFO: Stopping Coyote HTTP/1.1 on http-8080

3 answers

1 accepted

This widget could not be displayed.
Boris Berenberg Community Champion May 17, 2012

We tried a number of things to resolve this issue. Netstat showed that port 8005 was available. But JIRA would not bind to it. The machine is a member of AD and is regulated by Group Policy. Changing the port to 7005 made it work without issue.

This widget could not be displayed.

A number of causes that should be investigated:

1) port 8005 is in use, probably lingering

2) you try to bind port 8005 on the wrong IP (the configured ip is not the one from your box)

This widget could not be displayed.

Do not worry this is just becasue the installer is crap just like the java itself, even if it's ask you about the ports it's still use the default port for many things, shutdownport and etc, so you need to find them in the /conf/web.xml override them and then you will have a better chance to run that that ... something.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

78 views 0 1
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you