You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Szilard Antal (Jira)" <ji...@apache.org> on 2020/09/22 08:37:00 UTC

[jira] [Updated] (AMBARI-25552) Improve stack-trace disablement on HTTP 500 error response from the server

     [ https://issues.apache.org/jira/browse/AMBARI-25552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Szilard Antal updated AMBARI-25552:
-----------------------------------
    Status: Patch Available  (was: Open)

> Improve stack-trace disablement on HTTP 500 error response from the server
> --------------------------------------------------------------------------
>
>                 Key: AMBARI-25552
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25552
>             Project: Ambari
>          Issue Type: Task
>            Reporter: Szilard Antal
>            Assignee: Szilard Antal
>            Priority: Major
>             Fix For: 2.7.6
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> AMBARI-25353 disabling any stack trace output from API HTTP 500 response. The problem is that such response in most cases are no logged to the log file and later on production it would create a problem for customer to report the issue or for developer to investigate.
> The proposal is to enable logging for such errors with creating some request id, which would be added to log file and reported back to the user in format like: "Internal server error, please refer the exception by [request id] in the server log file"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)