nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

502 Proxy Error (Only on some Issues)

Wilhelm Krüger1

Hello Guys,

we have some proxy issues on our JIRA. When browsing in Project XY there appears the following error:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET/browse/XY-21.

Reason: Error reading from remote server

A piece of the error.log

[Mon Sep 17 11:45:10.269626 2012] [proxy:error] [pid 17364] [client xxx.xx.xx.xx:24971] AH00898: Error reading from remote server returned by /browse/XY-21, referer: https://xxxxxx/browse/XY-21

The strange thing is that this error only occurs on some special issues on this project. Other projects or issues are not affected by this problem.

Does anyone of you have an idea?

Regards,

Wilhelm

Accepted answers

Wilhelm Krüger1

Apparently there is a bug in JIRA - JRA-30068

We have already tested the JIRA 5.2 EAP and can confirm that this bug is fixed in JIRA 5.2

All comments

Nic Brough -Adaptavist-

What is "special" about these issues? What is different between them and the ones that work?

What does your Jira application log say?

Wilhelm Krüger1

I don't really know, i can't see any difference between those issues and the others.
And it only affects about three issues, all other issues are ok.

Some more information:

I was able to clone the issue by using the issue navigator, but i wasn't able to clone the attachments. So there might be some inconsistance in the database?!

I found those Information in the catalina.log (Is this similar to the application.log? If not where do I find it?)

Sep 17, 2012 11:23:45 AM com.sun.jersey.spi.container.servlet.WebComponent filterFormParameters
WARNING: A servlet POST request, to the URI https://xxxxxxxxx/rest/gadget/1.0/login, 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 @Fo
rmParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
Sep 17, 2012 11:49:46 AM com.sun.jersey.spi.container.servlet.WebComponent filterFormParameters
WARNING: A servlet POST request, to the URI https://xxxxxxxxx/rest/gadget/1.0/login, 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 @Fo
rmParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

Wilhelm Krüger1

part of the access.log

xxx.xxx.xx.xxx - - [17/Sep/2012:11:44:10 +0000] "GET /browse/XY-21 HTTP/1.1" 502 403 "https://xxxxxxxxxx/browse/XY-21" "Mozilla/5.0 (Maci
ntosh; Intel Mac OS X 10_7_4) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1"

Nic Brough -Adaptavist-

Not sure, those errors are more likely to be gadget or report errors, possibly caused by the same issues, but not the root cause of the problem.

Catalina.out is a good place to look, but I'd also check the application log (rather than random guesswork starting from "it's usually, but not always, jira-application.log"), go to Admin -> System information, that will tell you where the app log is)

As a hunch, can you compare the fields on the issues? For example, if you have a custom field called "Fred" and it's blank for working issues, and filled in with something on the broken ones? Are they all the same priority? Etc

Wilhelm Krüger1

Apparently there is a bug in JIRA - JRA-30068

We have already tested the JIRA 5.2 EAP and can confirm that this bug is fixed in JIRA 5.2

Vinay Sharma

Does anyone got solution to this problem?

Nic Brough -Adaptavist-

Posting on a 3 year old thread often doesn't do much as things have often moved on. But the *generic* answers here are still valid - you are going to need to establish the pattern of when it occurs and read the logs to see what errors you might be getting.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

issue

jira

proxy