[
https://issues.apache.org/jira/browse/LOG4J2-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15462723#comment-15462723
]
Remko Popma commented on LOG4J2-1560:
-------------------------------------
In general we are interested in helping other Apache projects (and any other
project) migrate to Log4j 2. Personally I haven't tried using Log4j 2 in an
environment with a security manager installed so I never ran into this.
I would say we are happy with all the help we can get. It would be great if you
could provide a failing test like Ralph suggested, and ideally a patch that
would make the test pass. If there is a way to run (some of) our existing tests
with a security manager that may also work. Open to suggestions...
> Log4j can lose exceptions when a security manager is present
> ------------------------------------------------------------
>
> Key: LOG4J2-1560
> URL: https://issues.apache.org/jira/browse/LOG4J2-1560
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.6.2
> Reporter: Jason Tedor
> Attachments: log4j-exception-logging-issue.tar.gz,
> throwable-proxy-security.exception.patch
>
>
> When Log4j is rendering an exception, it can attempt to load classes that it
> does not have permissions to load when a security manager is present.
> I have a patch and a failing test case for this; I will submit it shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
