logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Tedor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1560) Log4j can lose exceptions when a security manager is present
Date Sun, 04 Sep 2016 15:48:21 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15463103#comment-15463103
] 

Jason Tedor commented on LOG4J2-1560:
-------------------------------------

{quote}In general we are interested in helping other Apache projects (and any other project)
migrate to Log4j 2.{quote}

I'm a committer on Elasticsearch. It had been on our roadmap to migrate to Log4j 2, but our
plans were accelerated when we discovered that Log4j 1 is not compatible with Java 9 (it was
another committer to Elasticsearch that brought this to your [attention|http://mail-archives.apache.org/mod_mbox/logging-log4j-dev/201607.mbox/%3cCABLGb9z9aN0Krg_sgCjgt8sRpnONf8Tjp=x_ibJCAxWmUGz_OQ@mail.gmail.com%3e]
(originally on [jigsaw-dev|http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-July/008654.html]).

These security manager issues are a blocker for us. There is another issue on shutdown, although
I have not yet decided on the best course of action (I have a patch on our side, and a patch
on the Log4j side but I'm still deciding which is optimal).

{quote}I would say we are happy with all the help we can get.{quote}

I echo [~simonw]'s comments regarding being happy to help.



> 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


Mime
View raw message