By default, JIRA Standalone runs on port 8080 (and hence is available at (http://
<yourserver>:8080, eg. http://localhost:8080).
If you want to run another JIRA instance but already has a service claiming port 8080, there will be a conflict, and JIRA will fail to start. You may see errors like this:
This can be fixed by changing JIRA to use another listening port (eg. 8090) and shutdown port (eg. 8015). This is done by editing
conf\server.xml (eg. in Wordpad). The start of the file looks like:
Here, change the shutdown port from "8005" to "8015" and change the listening port from "8080" to "8090" (or some other free port — see below).
Then restart JIRA (bin\shutdown.bat; bin\startup.bat) and point a browser to http://
<yourserver>:8090 (eg. http://localhost:8090).
Which port number should I choose?
If you are not sure which port number to choose, use a tool such as netstat to determine which port numbers are free to use by JIRA. The highest port number that can be used is 65535 because it is the highest number which can be represented by an unsigned 16 bit binary number. The Internet Assigned Numbers Authority (IANA) lists the registration of commonly used port numbers for well-known Internet services, it's advisable to avoid any of those ports.
A note about firewalls
When you choose a port number for JIRA, bear in mind that your firewall may prevent people from connecting to JIRA based on the port number. Organisations with a local network protected by a firewall typically need to consider modifying their firewall configuration whenever they install a web-based application (such as JIRA) that is running on a new port or host. Even personal laptop and desktop machines often come with firewall software installed that necessitates the same sort of change as described above.
If JIRA does not need to be accessed from outside the firewall, then no firewall configuration changes will be necessary.