[
https://issues.apache.org/jira/browse/HADOOP-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792844#action_12792844
]
Steve Loughran commented on HADOOP-6452:
----------------------------------------
Trying to run under a security manager is a bit convoluted; you'd need to bring
up a process under one. You can't assume your unit test suite is allowed to
play with security managers as IDEs and even <junit> may use them to stop calls
to System.exit() working.
What I could test for is what triggered the problem in the stack trace, the
attempt to add permissions to the permissions object retrieved with
getPermissions(). That object has to support addPermissions(), which the
default clearly does not. This test should fit into a normal unit test method
> Hadoop JSP pages don't work under a security manager
> ----------------------------------------------------
>
> Key: HADOOP-6452
> URL: https://issues.apache.org/jira/browse/HADOOP-6452
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 0.21.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: hadoop-5740.patch, mapreduce-439-2.patch
>
>
> When you run Hadoop under a security manager that says "yes" to all security
> checks, you get stack traces when Jetty tries to initialise the JSP engine.
> Which implies you can't use Jasper under a security manager
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
