Crowd Application Is Ignoring http.nonProxyHosts Flag
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
The server administrator added the -Dhttp.nonProxyHosts property to the JAVA_OPTS definition, however the Applications contacting Crowd are not taking it into consideration.
For instance, all the server applications must use a proxy, but JIRA and Confluence (when accessing Crowd). The administrator added the Crowd Host to the http.nonProxyHosts property, however the Applications are still using the proxy to reach Crowd's APIs.
Cause
The XFire libraries located in the Application /lib folder do not have yet support for this Java property.
Resolution
Ensure that the Application is using library xfire-all-1.2.6.jar instead of the separated xfire-aegis-1.2.6.jar and xfire-core-1.2.6.jar files. Confluence is already shipped with xfire-all-1.2.6.jar (not for Confluence 3.3 and above due to CONF-20877), however JIRA is still using the separated files that can be replaced by the unique one with http.nonProxyHosts support.
Check if the -Dhttp.nonProxyHosts string has all the characters with this exact character case (the 'D', 'P' and 'H' uppercased and the remaining characters lowercased).
Was this helpful?