ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qiang Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RANGER-1280) Currently the ranger-admin will be aborted when the exception occured. We should get the default value instead of aborted.
Date Fri, 23 Dec 2016 06:46:58 GMT

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

Qiang Zhang updated RANGER-1280:
--------------------------------
    Description: 
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 strict tested our patch.

  was:
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.


> Currently the ranger-admin will be aborted 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
>
> 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 strict tested our patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message