[
https://issues.apache.org/jira/browse/LOG4J2-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555560#comment-15555560
]
Gary Gregory commented on LOG4J2-1560:
--------------------------------------
Thank you for contributing and following up.
"releasing 2.6.3 immediately as requested"
I wish it were as simple as pressing a button to create a release but it is
not.
A release manager needs to prepare an RC, and then release it. A normal release
candidates has a 3 day vetting process to allow the community to take the time
to review the release when its members can take the time to do so. In the case
of 2.7, it took two RCs to allow for some bug fixes.
> 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]
