Brett Walker created LOG4J2-2746:
------------------------------------
Summary: Change in shutdown behaviour between 2.12.1 and 2.13.0
Key: LOG4J2-2746
URL: https://issues.apache.org/jira/browse/LOG4J2-2746
Project: Log4j 2
Issue Type: Bug
Components: API
Affects Versions: 2.13.0
Environment: Apache Maven 3.6.2
(40f52333136460af0dc0d7232c0dc0bcf0d9e117; 2019-08-28T01:06:16+10:00)
Maven home: D:\Apache\Maven\3.6\bin\..
Java version: 11.0.5, vendor: AdoptOpenJDK, runtime: D:\Java\open-jdk-11
Default locale: en_AU, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Reporter: Brett Walker
Attachments: Log4J Shutdown Example.zip
The attached mavenised example demonstrated the observed behaviour.
In essence the following is observed:
{code:java}
// Shutdown Log4J2
LogManager.shutdown(); // line 1
// LogManager.shutdown(LogManager.getContext(false)); // line 2
Files.delete(logFile); // line 3
{code}
Using line 1; line 3 above should execute with no exceptions. For v2.12.1 this
is observed. For v2.13.0; line 3 throws an exception.
When line 2 is substituted for line 1. Line 3 executes with no exception for
both v2.12.1 and v2.13.0
I was able to determine that this behavior change was introduced by LOG4J2-2716
(253ada6ff2fb6c6a0dcfee8ed432372215f2ef78).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
