[
https://issues.apache.org/jira/browse/LOG4J2-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555567#comment-15555567
]
Remko Popma commented on LOG4J2-1560:
-------------------------------------
Doing a release is not a light task, and since we were getting ready to release
2.7 anyway I don't think anybody was willing to do the work to also crank out a
2.6.3 version.
Reading the previous comments on this ticket I can imagine how you may have
thought a 2.6.3 release was a possibility. Apologies for the confusion.
Looking at the code in master for ThrowableProxy and ThrowableProxyTest, it
looks as if the patch applied for LOG4J2-1563 has the same effect as the patch
attached to this ticket (but I am just eyeballing it, I could be missing
something). If I am correct we can close this ticket as fixed and update the
change log to show that this issue was also resolved in 2.7.
> 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-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: [email protected]
For additional commands, e-mail: [email protected]
