Loading...

Type: Bug
Resolution: Timed out
Priority: Low
Fix Version/s: None
Affects Version/s: 4.3.1, 4.3.2, 4.3.3
Component/s: Infrastructure & Services - Application Lifecycle
Labels:

Introduced in Version:
4.03
Symptom Severity:
Severity 3 - Minor
Current Status:

Hide

Atlassian Update – 04 December 2017

Hi everyone,

We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.

Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

Thank you,
Ignat Alexeyenko
Jira Bugmaster

Show
Atlassian Update – 04 December 2017 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

Summary of the bug:

HTTP dump logs do not show the html document responses in consistent manner. For example, the html document responses recorded in the dump log do not get fully logged and get suddenly cut.

Examples:

E.g. 1:

.........
			<html>
			<head>
				<title>Logging and Profiling</title>
			</head>
			
			
			<body>
...........................
...........................
			    <tr class="rowNormal">
			        <td>com.atlassian.jira.jql.resolver</td>
			        <td><strong>WARN</str
127.0.0.1 i979x126x1 davisn [26/May/2011:16:19:00 +0800] "GET http://localhost:8080/secure/Dashboard.jspa HTTP/1.1" - - - "http://localhost:8080/secure/admin/ViewLogging.jspa" "Mozilla/5.0 (Windows NT 6.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1" "1oex2a0"
127.0.0.1 o979x126x1 davisn [26/May/2011:16:19:00 +0800] "GET http://localhost:8080/secure/Dashboard.jspa HTTP/1.1" 200 42179 0.0670 "http://localhost:8080/secure/admin/ViewLogging.jspa" "Mozilla/5.0 (Windows NT 6.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1" "1oex2a0"
...........

E.g. 2:

..............
			<html>
			<head>
			    <content tag="section">home_link</content>
			    <script type="text/javascript">
			        AJS.$(document).ready(function() {
			            AJS.warnAboutFirebug(AJS.params.firebugWarning);
			
			            if(AJS.params.showWhitelistUpgradeWarning) {
			               var message = AJS.format(AJS.params.whitelistUpgradeText, '<a href="' + contextPath + '/secure/admin/ConfigureWhitelist!default.jspa?showUpgrade=true">', '</a>');
			                var $warning = AJS.$("<div id='applinks-upgrade-warning' class='global-warning'><p>" + message + "</p></div>");
			                    $warning.prependTo(AJS.$("body"));
			                }
			        });
			    </script>
			</head>
			    <body>
			        <fieldset class="hidden parameters">
			            <input type="hidden" id="firebugWarning" value="G'day mate! Firebug is known to cause performance problems with the JIRA dashboard. Try <a href='http://confluence.atlassian.com/x/xI72Cw'>disabling</a> it, if things are a bit slow.">
			            
			        </fieldset>
			        
			        <div class="dashboard-contents">
			            
			
			
			
			
			
			
			
			
			
			
			
			<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
			<html lang="en">
			<head>
			    <meta name="decorator" content="atl.general">
			    <title>System Dashboard</title>
			    
			    
			</head>
			<body>
.................

E.g. 3:

...........
<html><head><style type="text/css">body,td,div,span,p{font-family:arial,sans-serif;}a {color:#0000cc;}a:visited {color:#551a8b;}a:active {color:#ff0000;}body{margin: 0px;padding: 0px;background-color:white;}</style><script src="/plugins/servlet/gadgets/js/auth-refresh.js?v=a822b43a4487a77b93876dbbe766e54&container=atlassian&debug=0"></script><script>var gadgets=gadgets||{};
			gadgets.window=gadgets.window||{};
			(function(){gadgets.window.getViewportDimensions=function(){var A,B;
..........
			                        else{
			                            searchParam = AJS.gadget.fields.projectOrFilterPicker(gadget, "projectOrFilterId");
			                        }
			
			                        return  {
			                            action: "/rest/gadget/1.0/createdVsResolved/validate",
			                            theme : function(){
127.0.0.1 i979x129x1 davisn [26/May/2011:16:19:02 +0800] "GET http://localhost:8080/rest/gadget/1.0/createdVsResolved/generate HTTP/1.1" - - - "http://localhost:8080/plugins/servlet/gadgets/ifr?container=atlassian&mid=10051&country=US&lang=en&view=default&view-params=%7B%22writable%22%3A%22true%22%7D&st=atlassian%3Axv2NFzZciHBv5Ykt5nr%2FXLHDFwk5PGBON1Ib2WU9ObErvyS4qCrEBFOmGPK%2F1RS86h5i%2Bi8TwAoRw3QPkNG1zoE%2FIWc2QfGio%2B255pSjAePA%2BnWO8QvftsgaPRCjGGkjKv1CQS3eN7btZWHK7eSBNWtSL6VjpcZYXnlBeXEOAbj8FoqZ4W2hCw0fMRCVArf76mLMKZBlQNpQZdf1BSfq4Xzy3w8Y7Y3ku2Y2O8bCWWi3ZJ%2BgvwQyLKFH2n5LnXsKmyDzihBNvxRDGti623rXvO8jwcxgDetTK6TEjQl6TQSIHDKmUw4nP%2FwtQ9D1%2B3AOr%2F6aEHNqP1srVU%2B2B8NBDPd6OcE%3D&up_isConfigured=true&up_isPopup=false&up_refresh=false&up_projectOrFilterId=project-10016&up_daysprevious=150&up_periodName=weekly&up_versionLabel=all&up_isCumulative=false&up_showUnresolvedTrend=false&url=http%3A%2F%2Flocalhost%3A8080%2Frest%2Fgadgets%2F1.0%2Fg%2Fcom.atlassian.jira.gadgets%3Acreated-vs-resolved-issues-chart-gadget%2Fgadgets%2Fcreatedvsresolved-gadget.xml&libs=auth-refresh" "Mozilla/5.0 (Windows NT 6.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1" "1oex2a0"
127.0.0.1 o979x129x1 davisn [26/May/2011:16:19:02 +0800] "GET http://localhost:8080/rest/gadget/1.0/createdVsResolved/generate HTTP/1.1" 200 14733 0.2540 "http://localhost:8080/plugins/servlet/gadgets/ifr?container=atlassian&mid=10051&country=US&lang=en&view=default&view-params=%7B%22writable%22%3A%22true%22%7D&st=atlassian%3Axv2NFzZciHBv5Ykt5nr%2FXLHDFwk5PGBON1Ib2WU9ObErvyS4qCrEBFOmGPK%2F1RS86h5i%2Bi8TwAoRw3QPkNG1zoE%2FIWc2QfGio%2B255pSjAePA%2BnWO8QvftsgaPRCjGGkjKv1CQS3eN7btZWHK7eSBNWtSL6VjpcZYXnlBeXEOAbj8FoqZ4W2hCw0fMRCVArf76mLMKZBlQNpQZdf1BSfq4Xzy3w8Y7Y3ku2Y2O8bCWWi3ZJ%2BgvwQyLKFH2n5LnXsKmyDzihBNvxRDGti623rXvO8jwcxgDetTK6TEjQl6TQSIHDKmUw4nP%2FwtQ9D1%2B3AOr%2F6aEHNqP1srVU%2B2B8NBDPd6OcE%3D&up_isConfigured=true&up_isPopup=false&up_refresh=false&up_projectOrFilterId=project-10016&up_daysprevious=150&up_periodName=weekly&up_versionLabel=all&up_isCumulative=false&up_showUnresolvedTrend=false&url=http%3A%2F%2Flocalhost%3A8080%2Frest%2Fgadgets%2F1.0%2Fg%2Fcom.atlassian.jira.gadgets%3Acreated-vs-resolved-issues-chart-gadget%2Fgadgets%2Fcreatedvsresolved-gadget.xml&libs=auth-refresh" "Mozilla/5.0 (Windows NT 6.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1" "1oex2a0"

Notice in the examples 1 and 3 how the html document response logging looks interrupted suddenly and incomplete, although to the client he has actually received the whole document.
Also notice in example 2 that the document has 2 html headers whereas this is actually not the case.

Steps to reproduce:

From a fresh JIRA instance, simply enable http access dump logs and enter few pages. You will easily be able to see similar cases to the ones above as they are common and happen all over the log.

Impact analysis:

This would make it difficult to depend on the http dump logs to diagnose whether the server is sending the correct content or not. For example, I have had a customer who I needed to narrow the problem scope down whether it is his JIRA sending wrong content or whether it is the router/proxy/firewall altering the content and corrupting the document.

Regards,
Ali
Atlassian Support

Details

Description

Summary of the bug:

Examples:

E.g. 1:

E.g. 2:

E.g. 3:

Steps to reproduce:

Impact analysis:

Attachments

Activity

People

Dates