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 "Remko Popma (JIRA)" <ji...@apache.org> on 2016/10/08 13:28:20 UTC
[jira] [Closed] (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:all-tabpanel ]
Remko Popma closed LOG4J2-1560.
-------------------------------
Resolution: Fixed
Assignee: Gary Gregory
Fix Version/s: 2.7
Excellent, thank you for confirming.
Marking this issue as Fixed and closing it.
> 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
> Assignee: Gary Gregory
> Fix For: 2.7
>
> Attachments: log4j-exception-logging-issue.tar.gz, throwable-proxy-security-exception-2.6.2.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