Jira issue: post upgrade to jira 7.2.5

S Sujata November 24, 2016

I am getting below error post upgrade: 7.2.5

https://confluence.atlassian.com/jirakb/error-when-managing-application-access-in-jira-the-page-is-out-of-date-please-refresh-the-page-826875910.html

scenario 2 : Already present and still issues persists. but don't know whats that scenario 1. Please elaborate.

 

I did the following testing:

Added following below in server.xml: < Connector port="8080"

                   maxThreads="150"                    minSpareThreads="25"                    connectionTimeout="20000"

                   enableLookups="false"                    maxHttpHeaderSize="8192"                    protocol="HTTP/1.1"                    useBodyEncodingForURI="true"                    redirectPort="8443"                    acceptCount="100" disableUploadTimeout="true"/>

and when I hit http://ipaddress:8080... everything is working perfectly.

but when I edit in the following way in server.xmml: by adding proxy its showing the same error which I am getting in application access tab while adding the existing groups.

<Connector port="28080"

                   maxThreads="150"                    minSpareThreads="25"                    connectionTimeout="20000"

                   enableLookups="false"                    maxHttpHeaderSize="8192"                    protocol="HTTP/1.1"                    useBodyEncodingForURI="true"                    redirectPort="8443"                    acceptCount="100"                    disableUploadTimeout="true" scheme="https" proxyName="develop.qa.ampf.com" proxyPort="443"/>

So that mean, its proxy error. Please suggest the next steps

3 answers

1 vote
Vasiliy Zverev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 24, 2016
0 votes
S Sujata November 25, 2016

Ok, thanks for response. I degraded to 7.2.4 now. but still that issue persists.

and in apache I don't see such

Header unset Etag FileETag none in apache to enable as well. Please suggest.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 25, 2016
S Sujata December 1, 2016

Ok, can I know in which file the etag header exist for apache configuration. thanks.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 1, 2016

Depends on the version and type of apache you're using.  The docs for it will tell you.

S Sujata December 2, 2016

ok, can I get a code for enabling the etag in httpd.conf file. thanks.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 2, 2016

Please, read the docs.  It's in there.

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 25, 2016

Scenario 1 is a mis-configuration in your apache server.  You'll need to fix that.  It's not a JIRA server setting, it's apache.

And what Vasiliy said - you need to think about reverting to a supported version, or at least prepare to upgrade as soon as a supported higher version is available.

Suggest an answer

Log in or Sign up to answer