You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Qiang Zhang (JIRA)" <ji...@apache.org> on 2016/12/28 01:19:58 UTC
[jira] [Updated] (RANGER-1280) Currently the ranger-admin will be
aborted and couldn't find any error messages in log file when the exception
occured. We should get the default value instead of aborted.
[ https://issues.apache.org/jira/browse/RANGER-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Qiang Zhang updated RANGER-1280:
--------------------------------
Summary: Currently the ranger-admin will be aborted and couldn't find any error messages in log file when the exception occured. We should get the default value instead of aborted. (was: Currently the ranger-admin will be aborted when the exception occured. We should get the default value instead of aborted.)
> Currently the ranger-admin will be aborted and couldn't find any error messages in log file when the exception occured. We should get the default value instead of aborted.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RANGER-1280
> URL: https://issues.apache.org/jira/browse/RANGER-1280
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Reporter: Qiang Zhang
> Assignee: Qiang Zhang
> Labels: patch
> Attachments: 0001-RANGER-1280-Currently-the-ranger-admin-will-be-abort.patch
>
>
> I failed to run the ranger-admin command and couldn't find any error messages in log file after set ranger.service.http.connector.attrib.maxHeaderCount=aa(string value) in ranger-admin-site.xml file. I analyzed the source codes and found the reason.
> I found there are two questions after check the source codes in EmbeddedServer.java.
> 1. No exception pop out when called Integer.parseInt() and Long.parseLong() function. Once abnormal, the program aborted directly without log.
> 2. The catch captures anomaly without log in the loadConfig function. It only calls e.printStackTrace() function.
> Currently the program will be aborted when the exception occured. We should get the default value instead of aborted.
> We have tested our patch strictly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)