Modify conf/server.xml if running Jira standalone?

Brent Webster

I thought I only needed to update the /opt/atlassian/jira/conf/server.xml file if I was doing a WAR installation on an existing apache/tomcat server. I have currently modified /opt/atlassian/jira/bin/setenv.sh to update the JVM_SUPPORT_RECOMMENDED_ARGS variable to include settings for -Dhttp.nonProxyHosts, -Dhttps.proxyHost, Dhttps.proxyPort, Dhttp.proxyHost and Dhttp.proxyPort. Then I restarted Jira's java session with '/etc/init.d/jira restart' which calls '/opt/atlassian/jira/bin/startup.sh'

My IT guy recommended that I add the proxy settings in the server.xml file. Why?

Note: I'm in the process of trying to setup a Jira User Server for my Crucible server to use but I'm not having much luck.

BTW, does anyone have an original, unmodified 5.2.x server.xml file that I can reference.

Pedro Cora

While not obligatory, you can make changes to the server.xml if necessary.

The proxy settings that you added, are from a forward proxy (web proxy) to make JIRA able to reach the internet. If you also have a reverse proxy in front of JIRA, then you might need to add proxyName and proxyPort to the Tomcat connectors. For more information, take a look at our documentation at: https://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Apache

Here's a fresh server.xml from JIRA 5.2.11: http://pastie.org/private/nyqa00krsxpbh7thbripsw

-- Pedro