本文介绍了Glassfish 3.1.1突然停止写入server.log的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我更改了管理控制台中的一个日志级别,Glassfish 3.1.1停止了在domain1 / logs / server.log中写入任何内容。我自从恢复了更改,并尝试重新启动服务器几次。这是它记录的最后一件事:

I changed one of the log levels in the admin console, and Glassfish 3.1.1 stopped writing anything into the domain1/logs/server.log. I since reverted the change and tried restarting the server a couple times. Here's the last thing it logged:

[#|2012-02-20T16:44:53.738-0800|INFO|glassfish3.1.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=46;
_ThreadName=Thread-7;|com.sun.webui.jsf.component.DropDown::The current value of component form1:basicTable:rowGroup1:6:col3:level does not match any of the selections.
Did you forget to reset the value after changing the options? |#]


推荐答案

http://java.net/jira/browse/GLASSFISH-18205\">Glassfish-18205错误。
GFFileHandler日志记录级别可能设置为OFF。

Maybe you encountered Glassfish-18205 bug.GFFileHandler logging level might be set to "OFF".

尝试使用CLI将其设置为不同的级别:

Try to set it to a different level with CLI:

asadmin set-log-levels com.sun.enterprise.server.logging.GFFileHandler=ALL

您也可以使用管理控制台,但是下拉菜单不允许选择日志级别ALL(虽然这是一个有效的日志级别)。选择其中一个选项。

You could use the admin console as well, but the drop down menu there doesn't allow to select the log level "ALL" (although this is a valid log level). Choose one of the other options there.

这篇关于Glassfish 3.1.1突然停止写入server.log的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-04 18:41