Jira-Software 7.8.1 behind Apache 2.4 Reverse Proxy AJP (WARNING [ajp-nio-8009-exec-1])

[Patrick Kyne]

WARNING [ajp-nio-8009-exec-1] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://external_hostname_domain.fqdn/jira/rest/activity-stream/1.0/preferences?_=1522779982770, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

Above error pops while trying to access some elevated-permission pages to reset user's password, change permissions, etc.

[Josh Steckler]

Are you having problems using a particular function of Jira?

Sometimes it's best to ignore warning messages in the logs.

[Patrick Kyne]

Yes sir.

If I go to edit users, I can elevate permissions (re-enter my password). I am able to browse users, but if I select a user, sometimes it will let me see the user screen, but usually it presents me with a 403 not authorized error. My configs are posted in the ticket:   https://community.atlassian.com/t5/Jira-questions/Jira-Software-7-8-1-w-Apache-2-4-Reverse-Proxy-Errors/qaq-p/762699

I am the SA & Jira-Admin. I only seem to have the issues with elevated-permission activities while going through the Apache reverse proxy as I seem to be able to work fine when connecting locally over port 8080.

[Patrick Kyne]

Going through Apache Reverse Proxy (AJP): If, after elevating permissions, from the user browser screen, I click on the Edit link for a user, I receive the following message:

Communications Breakdown

The JIRA server was contacted but has returned an error response. We are unsure of the result of this operation.

Close this dialog and press refresh in your browser.

And then, I generally have to log out to get back in.

[Josh Steckler]

You need a ServerName directive in your apache conf file, in the 443 virtualhost:

ServerName externalservername.fqdn

[Josh Steckler]

Oh never mind, you do have one. 

Is it possible it's a matter of ordering the directives? Put the ServerName above the proxy config

[Patrick Kyne]

I've tried re-ordering the vhost.conf file with the ServerName above the proxy config, and didn't seem to make any difference.