|
By default, JIRA Standalone runs on port 8080 (and hence is available at (http://<yourserver>:8080, eg. http://localhost:8080). If the server on which you run JIRA Standalone already has a service claiming port 8080, there will be a conflict, and JIRA will fail to start. You may see errors like this: LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use:8080 This can be fixed by changing JIRA to use another port (eg. 8090). This is done by editing conf\server.xml (eg. in Wordpad). The start of the file looks like: <Server port="8005" shutdown="SHUTDOWN"> <Service name="Catalina"> <Connector port="8080" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" /> Here, change "8005" to "8006", and change "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
Which port number should I choose? If you are not sure which port number to choose, try new numbers one by one, starting with default port numbers and incrementing by one. Keep going until you find an available port number.
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.
|
Labels
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.
Comments (3)
Dec 05, 2006
Jeff Heinen says:
Lets say that instead of moving the port, you want to add an additional po...Lets say that instead of moving the port, you want to add an additional port to which the service is listening. (Meaning: allow both port 8080 and 8090 to accept requests to the same server process).
Would that simply be another "<Connector" item? And what effect would that have on the process in terms of load and how it handles requests?
Dec 10, 2006
Jeff Turner says:
> Would that simply be another "<Connector" item? Yes. > And what eff...> Would that simply be another "<Connector" item?
Yes.
> And what effect would that have on the process in terms of load and how it handles requests?
It shouldn't have any effect. It's just another possible source of incoming requests.
Oct 16, 2008
Tim Spears says:
I suggest adding a comment here about binding to a specified address using <C...I suggest adding a comment here about binding to a specified address using <Connector port="443" address="10.1.3.5"...> for example. This information was rather hard to come by in the documentation I could find, and it may even be worth including address="0.0.0.0' in the template/default server.xml.
Add Comment