Daniel Fuchs 5f717a6674 7184195: java.util.logging.Logger.getGlobal().info() doesn't log without configuration
Due to subtle synchronization issues between LogManager & Logger class initialization the global logger doesn't have its 'manager' field initialized until the LogManager is initialized. This fix will ensure that the global logger has its 'manager' field set when getGlobal() is called.

Reviewed-by: mchung, plevart
2013-07-02 19:47:58 +02:00

43 lines
1.5 KiB
Java

/*
* Copyright (c) 2013, Oracle and/or its affiliates. All rights reserved.
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
*
* This code is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License version 2 only, as
* published by the Free Software Foundation.
*
* This code is distributed in the hope that it will be useful, but WITHOUT
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
* version 2 for more details (a copy is included in the LICENSE file that
* accompanied this code).
*
* You should have received a copy of the GNU General Public License version
* 2 along with this work; if not, write to the Free Software Foundation,
* Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
*
* Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
* or visit www.oracle.com if you need additional information or have any
* questions.
*/
package testgetglobal;
import java.util.logging.LogManager;
import java.util.logging.Logger;
/**
* This class is used to verify that calling Logger.getGlobal() in the static
* initializer of a LogManager subclass installed as default LogManager
* does not cause issues.
* @author danielfuchs
*/
public class LogManagerImpl1 extends LogManager {
static final Logger global;
static {
global = Logger.getGlobal();
System.err.println("Global is: " + global);
}
}