I made an update from Jira 64-bit 5.1.7 to 5.2.2 and Jira won't start.
I discovered that the problem is related to the JVM_SUPPORT_RECOMMENDED_ARGS variable in JIRA_HOME/bin/setenv.sh.
It read: JVM_SUPPORT_RECOMMENDED_ARGS=-Dhttp.proxyHost=proxy.company.com -Dhttp.proxyPort=8080 -Dhttp.nonProxyHosts=**.internal.company.com|*.company.net|localhost|127.0.0.1|192.168.169.*
The logfile /usr/local/jira/std/logs/catalina.out reports:
eval: 1: 127.0.0.1: not found
eval: 1: *.company.net: not found
eval: 1: localhost: not found
eval: 1: 192.168.169.*: not found
If I reduce the nonProxyHosts to one entry so that there is no pipe symbol, Jira will start.
The variable reads now: JVM_SUPPORT_RECOMMENDED_ARGS=-Dhttp.proxyHost=proxy.clausjuergens.de -Dhttp.proxyPort=8080 -Dhttp.nonProxyHosts=*.company.net.
The problem does not occure with Jira 5.1.7 and all prior versions we run.
We need multiple exceptions for the proxy use. What delimiter should be used now? Or is there a bug that the pipe symbol is interpreted as a shell pipe though it should not be.
Thanks in advance,
I surrounded the proxy exceptions by escaped quotation-marks and now ist works.
So the whole variable setting looks like this:
JVM_SUPPORT_RECOMMENDED_ARGS="-Dhttp.proxyHost=proxy.company.com -Dhttp.proxyPort=8080 -Dhttp.nonProxyHosts=\"*.internal.company.com|*.company.net|localhost|127.0.0.1|192.168.169.*\""
The asterisk (*) was not the problem. It was the pipe (|).
Thanks for your suggestion and sorry for my typo (**)
I was just about to hit the post button when I noticed you had "Dhttp.nonProxyHosts=**.internal.company.com"
This could just be a typo in the forum post but I don't think you should have the two *'s there, I think it should be "Dhttp.nonProxyHosts=*.internal.company.com|"
I had issues with the proxy settings as well but, I don't think it was the same issue your having but, I think my solution might help. Our solution was to move the setting to the catalina.properties file instead of using java args. The list of config options follow:
http.proxyHost=0.0.0.0 http.proxyPort=8080 https.proxyHost=0.0.0.0 https.proxyPort=8080 http.proxyUser=<Proxy User> http.proxyPassword=<Proxy Pass> http.nonProxyHosts=*.local|devmachine|someothermachine #For Active Directory Auth http.auth.ntlm.domain=<domain> http.proxyAuth=ntlm
You may not need to set both the http and https proxy settings.
For me, it seems that you forget the Quotes:
JVM_SUPPORT_RECOMMENDED_ARGS="-Dhttp.proxyHost=proxy.company.com -Dhttp.proxyPort=8080 -Dhttp.nonProxyHosts=**.internal.company.com|*.company.net|localhost|127.0.0.1|192.168.169.*"
The only way I have been able to get wildcards working in my nonProxyHosts settings for either JIRA or Confluence running on CentOS was to move them to catalina.properties as per Jason Henlers suggestion. Even Atlassian Support couldn't help me and told me to talk to Oracle.
And even then, wildcards on the nonProxyJosts lines are ignored on JIRA (6.2.3), but not for Confluence.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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!
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