[
https://issues.apache.org/jira/browse/LOG4J2-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15463068#comment-15463068
]
Jason Tedor commented on LOG4J2-1560:
-------------------------------------
It's early September, so "this month" is a rather wide range; can you offer a
narrower range? We have a hack in place now to workaround this issue but would
strongly prefer to never have to ship it.
If there is a timely 2.6.3 release, I would like to see LOG4J2-1506 backported
as well as this is another issue that we are running into currently on 2.6.2
(we run with the security manager and we are not granting the permissions that
Log4j wants for JMX, so we explicitly disable the use of JMX and hit this issue
on shutdown). This is another place where we are going to otherwise have to put
a hack in place.
> 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]
