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 "Gary Gregory (JIRA)" <ji...@apache.org> on 2017/02/22 03:53:44 UTC
[jira] [Comment Edited] (LOG4J2-1820) Log4j 2.8 can lose exceptions
when a security manager is present
[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877426#comment-15877426 ]
Gary Gregory edited comment on LOG4J2-1820 at 2/22/17 3:53 AM:
---------------------------------------------------------------
What about the other 31 call sites we have to {{Class.getClassLoader()}}? Wouldn't these need special care as well? Should the try/catch be abstracted in a utility method? (I'm not separating test from main in the 31 count, it's just what Eclipse reports.)
was (Author: garydgregory):
What about the other 31 call sites we have to {{Class.getClassLoader()}}? Wouldn't these need special care as well? Should the try/catch be abstracted in a utility method?
> Log4j 2.8 can lose exceptions when a security manager is present
> ----------------------------------------------------------------
>
> Key: LOG4J2-1820
> URL: https://issues.apache.org/jira/browse/LOG4J2-1820
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.8
> Reporter: Jason Tedor
> Attachments: 0001-Handle-security-exception-on-getting-class-loader.patch
>
>
> When Log4j is rendering an exception, it can attempt to access a class loader that it does not have permissions to access when a security manager is present.
> I have a patch and a failing test case for this; I will submit it shortly.
> This is similar to LOG4J2-1560.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org