N.B。虽然我还没有设法解决问题的最终解决方案,但在Andreas的帮助下,我能够意识到我已经错误地配置了log4j并且它使用的是默认属性文件,而不是我自己指定的那个。我将在适当的时候发布解决方案,以便将来可供人们使用......就在本周末的10月之后:D
好的,所以我知道这里已经提出了类似的问题,但是我还没有找到一个有相同问题的帖子或解决它的解决方案。
好的,所以我尝试开始使用log4j来尝试并习惯使用我的代码进行正确的日志记录(最佳实践!)但是在尝试修复代码中的错误时遇到了一些问题。问题是我需要读取控制台输出,但log4j将所有内容放在那里(DEBUG)。起初这不是一个问题,所以我没有费心去让log4j停止这样做。但现在我发现很难在输出中查找我需要的信息。
作为我的问题的快速解决方案,我尝试以编程方式将记录器级别的日志记录级别更改为OFF。
然后我尝试更改属性文件以防止它写入控制台,nope。
然后我尝试删除属性文件中的所有内容,认为log4j不再知道如何表现,nope。
然后我尝试通过注释掉所有的行而不是初始化任何记录器来完全删除我的代码中的log4j,nope ...等等,是什么?
是的,似乎即使我的项目中没有任何log4j代码,log4j也不想停止。
此时我试图清理项目(我使用eclipse),然后我尝试重新启动eclipse,然后重启我的笔记本电脑。
我知道我可能会进行大规模的疏忽,但我觉得评论所有代码都会做点什么。
我应该注意到,我试过没有对正在打印的内容产生任何影响,它总是以相同的顺序打印相同的行(因此我确定我做错了什么)
非常感谢能提供的任何帮助
编辑1:我还应该声明我认为是导致问题的log4j的原因是控制台中的所有输出都采用我在log4j.properties文件中定义的格式。
编辑2:
一个班级
public class MessageSender extends AbstractCommand{
//private static final Logger LOG = Logger.getLogger(HelloWorldCommandFactory.class);
private String messageText = "placeholder";
private final long MESSAGE_ID = XXXXXXXXXX;
@Override
public void execute() {
try {
//LOG.setLevel(Level.OFF);
//LOG.info("MESSAGE_TEXT: "+messageText);
TelegramRequest telegramRequest = TelegramRequestFactory.createSendMessageRequest(MESSAGE_ID, messageText, true, null, null);
//LOG.info("REQUEST: "+telegramRequest.equals(getRequestHandler()));
requestHandler.sendRequest(telegramRequest);
} catch (JsonParsingException | TelegramServerException e) {
e.printStackTrace();
}
}
public MessageSender(Message message, RequestHandler requestHandler){
super(message, requestHandler);
}
public MessageSender(Message message, RequestHandler requestHandler, String text){
super(message, requestHandler);
this.messageText = text;
}
另一个班级
public class MyCommandFactory implements CommandFactory {
//private static final Logger LOG = Logger.getLogger(MyCommandFactory.class);
@Override
public Command createCommand(Message message, RequestHandler requestHandler) {
//LOG.setLevel(Level.OFF);
//LOG.info("MESSAGE_ID: "+message.getChat().getId()+" MESSAGE_BODY: "+message.getText());
return new MessageSender(message, requestHandler);
}
}
输出样本(我删除了某些敏感信息)
15-09-25 06:32:42 INFO AbstractCommandDispatcher:69 - *************************************
2015-09-25 06:32:42 INFO AbstractCommandDispatcher:70 - ** Starting up command dispatcher...
2015-09-25 06:32:42 INFO AbstractCommandDispatcher:71 - *************************************
2015-09-25 06:32:43 INFO AbstractCommandWatcher:50 - >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2015-09-25 06:32:43 INFO AbstractCommandWatcher:51 - >> Starting up command watcher...
2015-09-25 06:32:43 INFO AbstractCommandWatcher:52 - >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2015-09-25 06:32:45 DEBUG DefaultCommandWatcher:104 - Polling Telegram updates (offset:0, limit:100, timeout=0)...
2015-09-25 06:32:45 DEBUG RequestAddCookies:122 - CookieSpec selected: default
2015-09-25 06:32:45 DEBUG RequestAuthCache:76 - Auth cache not set in the context
2015-09-25 06:32:45 DEBUG PoolingHttpClientConnectionManager:249 - Connection request: [route: {s}->https://api.telegram.org:443][total kept alive: 0; route allocated: 0 of 2; total allocated: 0 of 20]
2015-09-25 06:32:45 DEBUG PoolingHttpClientConnectionManager:282 - Connection leased: [id: 0][route: {s}->https://api.telegram.org:443][total kept alive: 0; route allocated: 1 of 2; total allocated: 1 of 20]
2015-09-25 06:32:45 DEBUG MainClientExec:234 - Opening connection {s}->https://api.telegram.org:443
2015-09-25 06:32:46 DEBUG DefaultHttpClientConnectionOperator:131 - Connecting to api.telegram.org/
2015-09-25 06:32:46 DEBUG SSLConnectionSocketFactory:335 - Connecting socket to api.telegram.org/ with timeout 0
2015-09-25 06:32:46 DEBUG SSLConnectionSocketFactory:388 - Enabled protocols: [TLSv1, TLSv1.1, TLSv1.2]
2015-09-25 06:32:46 DEBUG SSLConnectionSocketFactory:389 - Enabled cipher suites:[TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_ECDSA_WITH_RC4_128_SHA, TLS_ECDHE_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_RC4_128_SHA, TLS_ECDH_ECDSA_WITH_RC4_128_SHA, TLS_ECDH_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_RC4_128_MD5, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
2015-09-25 06:32:46 DEBUG SSLConnectionSocketFactory:393 - Starting handshake
2015-09-25 06:32:46 DEBUG SSLConnectionSocketFactory:423 - Secure session established
2015-09-25 06:32:46 DEBUG SSLConnectionSocketFactory:424 - negotiated protocol: TLSv1.2
2015-09-25 06:32:46 DEBUG SSLConnectionSocketFactory:425 - negotiated cipher suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
2015-09-25 06:32:46 DEBUG SSLConnectionSocketFactory:433 - peer principal: CN=api.telegram.org, OU=Domain Control Validated
2015-09-25 06:32:46 DEBUG SSLConnectionSocketFactory:442 - peer alternative names: [api.telegram.org, www.api.telegram.org]
2015-09-25 06:32:46 DEBUG SSLConnectionSocketFactory:446 -
2015-09-25 06:32:46 DEBUG DefaultHttpClientConnectionOperator:138 - Connection established
2015-09-25 06:32:46 DEBUG MainClientExec:255 - Executing request POST
2015-09-25 06:32:46 DEBUG MainClientExec:260 - Target auth state: UNCHALLENGED
2015-09-25 06:32:46 DEBUG MainClientExec:266 - Proxy auth state: UNCHALLENGED
2015-09-25 06:32:46 DEBUG headers:124 - http-outgoing-0 >>
2015-09-25 06:32:46 DEBUG headers:127 - http-outgoing-0 >> Content-Length: 28
2015-09-25 06:32:46 DEBUG headers:127 - http-outgoing-0 >> Content-Type: application/x-www-form-urlencoded; charset=UTF-8
2015-09-25 06:32:46 DEBUG headers:127 - http-outgoing-0 >> Host: api.telegram.org
编辑3:
log4j.properties文件
log4j.rootLogger=INFO, CONSOLE
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern= %d{HH:mm:ss,SSS} [%t] %-5p %x %C{1} : %m%n
答案 0 :(得分:4)
您可以将级别更改为 OFF ,这样可以清除所有日志记录。根据log4j网站,有效级别按重要性顺序为 TRACE , DEBUG , INFO , WARN ,< strong>错误,致命。有一个名为 OFF 的未记录级别,它比FATAL更高级别,并关闭所有日志记录。
在采用程序化方法时,您是否正确?我就是这样做的 -
List<Logger> loggers = Collections.<Logger>list(LogManager.getCurrentLoggers());
loggers.add(LogManager.getRootLogger());
for ( Logger logger : loggers ) {
logger.setLevel(Level.OFF);
}
另外,您也可以像Logger.getRootLogger().removeAllAppenders();
Logger.getRootLogger().addAppender(new NullAppender());
一样完成command line tool
eclipse
。
确保重新启动项目的clean build
和log4j.properties
,以使更改生效。
如果上述方法无效 -
创建classpath
文件并将该文件放在应用程序的contents
中。将以下log4j.debug=FALSE
log4j.rootLogger=INFO, R
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=C:/apache-tomcat-5.5.27/logs/testlog.log
log4j.appender.R.MaxFileSize=100KB
log4j.appender.R.MaxBackupIndex=5
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%d{yyyy-MM-dd HH\:mm\:ss.SSSS} %p %t %c - %m%n
粘贴到同一个 -
my_options = {"bg" : "gray60", "font" : ("Tahoma", 20)}
tk.Label(root, text = "Same background", **my_options).grid(row = 1, column = 1)
tk.Button(root, text = "and font.", **my_options).grid(row = 1, column = 2, padx = (5, 0))