Question

更新我犯了一个错误，我忽略了整个过程。我的logging.properties文件在文件名中有一个我不知道的尾随空格。我不知道它是如何进入的，但是一旦我删除了那个空间，一切都有效。我的问题是我提供了错误的名称，即没有尾随空格的文件名。

我不明白java.util.logging是如何运作的。我正在尝试复制以下提供的示例代码： Java Practices -> Logging messages

我首先在 Eclipse中创建了一个空的Java项目。我在包SimpleLogger.java中创建了一个类myapp.business。在resources下，我放了logging.properties。我没有任何编译问题，我可以单步执行代码，但我无法弄清楚输出在哪里？

SimpleLogger.java看起来像：

package myapp.business;

import java.util.logging.Level;
import java.util.logging.Logger;

public final class SimpleLogger {

  public static void main(String... args) {
    SimpleLogger thing = new SimpleLogger();
    thing.doSomething();
  }

  public void doSomething() {
    // Log messages, one for each level
    // The actual logging output depends on the configured
    // level for this package. Calls to "inapplicable"
    // messages are inexpensive.
    fLogger.finest("this is finest");
    fLogger.finer("this is finer");
    fLogger.fine("this is fine");
    fLogger.config("this is config");
    fLogger.info("this is info");
    fLogger.warning("this is a warning");
    fLogger.severe("this is severe");

    // In the above style, the name of the class and
    // method which has generated a message is placed
    // in the output on a best-efforts basis only.
    // To ensure that this information is always
    // included, use the following "precise log"
    // style instead :
    fLogger.logp(Level.INFO, this.getClass().toString(), "doSomething", "blah");

    // For the very common task of logging exceptions, there is a
    // method which takes a Throwable :
    Throwable ex = new IllegalArgumentException("Some exception text");
    fLogger.log(Level.SEVERE, "Some message", ex);

    // There are convenience methods for exiting and
    // entering a method, which are at Level.FINER :
    fLogger.exiting(this.getClass().toString(), "doSomething");

    // Display user.home directory, if desired.
    // (This is the directory where the log files are generated.)
    // System.out.println("user.home dir: " +
    // System.getProperty("user.home") );
  }

  // PRIVATE

  // This style has no hard-coded literals, and requires the logger
  // to be non-static.
  private final Logger fLogger = Logger.getLogger(this.getClass().getPackage().getName());

  // This style lets the logger be static, but hard-codes a class literal.
  // private static final Logger fLogger =
  // Logger.getLogger(SimpleLogger.class.getPackage().getName())
  // ;

  // This style uses a hard-coded literal and should likely be avoided:
  // private static final Logger fLogger = Logger.getLogger("myapp.business");
}

logging.properties目录中的resources如下所示：

# Properties file which configures the operation of the JDK 
# logging facility.

# The system will look for this config file, first using 
# a System property specified at startup: 
# 
# >java -Djava.util.logging.config.file=myLoggingConfigFilePath 
# 
# If this property is not specified, then the config file is 
# retrieved from its default location at: 
# 
# JDK_HOME/jre/lib/logging.properties

# Global logging properties. 
# ------------------------------------------ 
# The set of handlers to be loaded upon startup. 
# Comma-separated list of class names. 
# (? LogManager docs say no comma here, but JDK example has comma.) 
handlers=java.util.logging.FileHandler, java.util.logging.ConsoleHandler

# Default global logging level. 
# Loggers and Handlers may override this level 
.level=INFO

# Loggers 
# ------------------------------------------ 
# Loggers are usually attached to packages. 
# Here, the level for each package is specified. 
# The global level is used by default, so levels 
# specified here simply act as an override. 
myapp.ui.level=ALL 
myapp.business.level=CONFIG 
myapp.data.level=SEVERE

# Handlers 
# -----------------------------------------

# --- ConsoleHandler --- 
# Override of global logging level 
java.util.logging.ConsoleHandler.level=SEVERE 
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter

# --- FileHandler --- 
# Override of global logging level 
java.util.logging.FileHandler.level=ALL

# Naming style for the output file: 
# (The output file is placed in the directory 
# defined by the "user.home" System property.) 
java.util.logging.FileHandler.pattern=%h/java%u.log

# Limiting size of output file in bytes: 
java.util.logging.FileHandler.limit=50000

# Number of output files to cycle through, by appending an 
# integer to the base file name: 
java.util.logging.FileHandler.count=1

# Style of output (Simple or XML): 
java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter

在 Eclipse 中的运行配置中，我的Main类为myapp.business.SimpleLogger，我的VM参数为-Djava.util.logging.config.file=resources/logging.properties

我在控制台上看不到任何内容，也无法找到任何* .log文件。如果有帮助的话，我在 Ubuntu 16.10 上运行它。

修改：回应 pvg 我试图将 Eclipse 中的VM参数更改为：-Djava.util.logging.config.file=/home/myusername/EclipseWorkspace/Temp/resources/logging.properties

我也尝试通过bin目录中的命令行调用它：

java -Djava.util.logging.config.file=/home/myusername/EclipseWorkspace/Temp/resources/logging.properties -cp . myapp.business.SimpleLogger

这也不起作用，即我没有看到任何输出，也没有在任何地方看到* .log文件。

Answer 1

对我来说，只有将整个路径放在Eclipse VM参数中才有效：

-Djava.util.logging.config.file=/whole/path/of/logging.properties

然后，将根据logging.properties文件中配置的内容创建输出文件。在这种情况下：

# Naming style for the output file: 
# (The output file is placed in the directory 
# defined by the "user.home" System property.) 
java.util.logging.FileHandler.pattern=%h/java%u.log

输出文件将在用户的主目录中创建。在我的情况下，创建的文件名为java0.log - %u表示＆＃34;解决冲突的唯一编号＆＃34; （也就是自动生成的编号，以避免出现文件同名;在我的例子中，它是0）。

Answer 2

...但我无法弄清楚输出在哪里？

使用以下代码获取工作目录并列出可以告诉您主目录的环境。此示例还尝试使用LogManager设置创建文件处理程序。

public static void main(String[] args) throws IOException {
    System.out.println("Working directory=" + new File(".").getCanonicalPath());
    for (Map.Entry<String, String> e : System.getenv().entrySet()) {
        System.out.println(e);
    }
    new FileHandler().close();
}

java.util.logging日志文件或输出在哪里？

2 个答案: