You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Jason Tedor (JIRA)" <ji...@apache.org> on 2016/09/02 18:15:20 UTC
[jira] [Commented] (LOG4J2-1560) Log4j can lose exceptions when a
security manager is present
[ https://issues.apache.org/jira/browse/LOG4J2-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15459218#comment-15459218 ]
Jason Tedor commented on LOG4J2-1560:
-------------------------------------
This issue is a blocker for Elasticsearch; is there any possibility of an imminent 2.6.3 patch release containing this fix?
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org