堆栈内存溢出
  简体   繁体   English

如何停止码头应用程序中的登录

[英]How to stop logging in jetty application

 原文  2017-10-03 08:40:32  1   3    java/ jetty/ logback/ slf4j/ embedded-jetty

问题描述

I am using jetty to implement websocket client. 我正在使用码头实施websocket客户端。 This is producing a lot of noise in log file in start up of application and when failed reconnect websocket. 在应用程序启动以及重新连接Websocket失败时，这会在日志文件中产生大量噪音。 Actually in case of websocket connection failure i am retrying after a minute so after every minute it it producing this kind of log: 实际上，在websocket连接失败的情况下，我会在一分钟后重试，因此每分钟后它会生成这种日志： 

2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.log:173 - Logging to Logger[org.eclipse.jetty.util.log] via org.eclipse.jetty.util.log.Slf4jLog
2017-06-12 14:23:04 | INFO  | [main] c.h.h.v.c.WebSocketListener:53 - STARTING WS Client
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:184 - starting org.eclipse.jetty.websocket.client.WebSocketClient@179d4544
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.w.c.WebSocketClient:157 - Starting org.eclipse.jetty.websocket.client.WebSocketClient@179d4544
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.ContainerLifeCycle:302 - org.eclipse.jetty.websocket.client.WebSocketClient@179d4544 added {WebSocketClient@396182852{STOPPED,8<=0<=200,i=0,q=0},AUTO}
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.ContainerLifeCycle:302 - org.eclipse.jetty.websocket.client.WebSocketClient@179d4544 added {org.eclipse.jetty.io.MappedByteBufferPool@19487c31,POJO}
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.ContainerLifeCycle:302 - org.eclipse.jetty.websocket.client.WebSocketClient@179d4544 added {org.eclipse.jetty.util.thread.ScheduledExecutorScheduler@2f9dc6f7,AUTO}
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.ContainerLifeCycle:302 - org.eclipse.jetty.websocket.client.WebSocketClient@179d4544 added {org.eclipse.jetty.websocket.client.io.ConnectionManager@36f6de04,AUTO}
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:184 - starting WebSocketClient@396182852{STOPPED,8<=0<=200,i=0,q=0}
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:177 - STARTED WebSocketClient@396182852{STARTED,8<=8<=200,i=7,q=0}
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:184 - starting org.eclipse.jetty.util.thread.ScheduledExecutorScheduler@2f9dc6f7
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:177 - STARTED org.eclipse.jetty.util.thread.ScheduledExecutorScheduler@2f9dc6f7
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:184 - starting org.eclipse.jetty.websocket.client.io.ConnectionManager@36f6de04
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.ContainerLifeCycle:302 - org.eclipse.jetty.websocket.client.io.ConnectionManager@36f6de04 added {org.eclipse.jetty.websocket.client.io.WebSocketClientSelectorManager@1cbbbc31,AUTO}
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:184 - starting org.eclipse.jetty.websocket.client.io.WebSocketClientSelectorManager@1cbbbc31
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:184 - starting org.eclipse.jetty.io.SelectorManager$ManagedSelector@78fb787f keys=-1 selected=-1
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:177 - STARTED org.eclipse.jetty.io.SelectorManager$ManagedSelector@78fb787f keys=0 selected=0
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.t.QueuedThreadPool:342 - WebSocketClient@396182852{STARTED,8<=8<=200,i=8,q=0} dispatched org.eclipse.jetty.io.SelectorManager$ManagedSelector@78fb787f keys=0 selected=0
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:184 - starting org.eclipse.jetty.io.SelectorManager$ManagedSelector@224dc69c keys=-1 selected=-1
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-10-selector-0] o.e.j.i.SelectorManager:418 - Starting Thread[WebSocketClient@396182852-10-selector-0,5,main] on org.eclipse.jetty.io.SelectorManager$ManagedSelector@78fb787f keys=0 selected=0
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:177 - STARTED org.eclipse.jetty.io.SelectorManager$ManagedSelector@224dc69c keys=0 selected=0
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-10-selector-0] o.e.j.i.SelectorManager:443 - Selector loop waiting on select
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.t.QueuedThreadPool:342 - WebSocketClient@396182852{STARTED,8<=8<=200,i=7,q=0} dispatched org.eclipse.jetty.io.SelectorManager$ManagedSelector@224dc69c keys=0 selected=0
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:184 - starting org.eclipse.jetty.io.SelectorManager$ManagedSelector@7bfaa588 keys=-1 selected=-1
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-13-selector-1] o.e.j.i.SelectorManager:418 - Starting Thread[WebSocketClient@396182852-13-selector-1,5,main] on org.eclipse.jetty.io.SelectorManager$ManagedSelector@224dc69c keys=0 selected=0
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:177 - STARTED org.eclipse.jetty.io.SelectorManager$ManagedSelector@7bfaa588 keys=0 selected=0
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-13-selector-1] o.e.j.i.SelectorManager:443 - Selector loop waiting on select
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.t.QueuedThreadPool:342 - WebSocketClient@396182852{STARTED,8<=8<=200,i=6,q=0} dispatched org.eclipse.jetty.io.SelectorManager$ManagedSelector@7bfaa588 keys=0 selected=0
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:184 - starting org.eclipse.jetty.io.SelectorManager$ManagedSelector@489c34f keys=-1 selected=-1
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-14-selector-2] o.e.j.i.SelectorManager:418 - Starting Thread[WebSocketClient@396182852-14-selector-2,5,main] on org.eclipse.jetty.io.SelectorManager$ManagedSelector@7bfaa588 keys=0 selected=0
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:177 - STARTED org.eclipse.jetty.io.SelectorManager$ManagedSelector@489c34f keys=0 selected=0
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-14-selector-2] o.e.j.i.SelectorManager:443 - Selector loop waiting on select
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.t.QueuedThreadPool:342 - WebSocketClient@396182852{STARTED,8<=8<=200,i=5,q=0} dispatched org.eclipse.jetty.io.SelectorManager$ManagedSelector@489c34f keys=0 selected=0
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:177 - STARTED org.eclipse.jetty.websocket.client.io.WebSocketClientSelectorManager@1cbbbc31
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-15-selector-3] o.e.j.i.SelectorManager:418 - Starting Thread[WebSocketClient@396182852-15-selector-3,5,main] on org.eclipse.jetty.io.SelectorManager$ManagedSelector@489c34f keys=0 selected=0
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:177 - STARTED org.eclipse.jetty.websocket.client.io.ConnectionManager@36f6de04
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-15-selector-3] o.e.j.i.SelectorManager:443 - Selector loop waiting on select
2017-06-12 14:23:04 | INFO  | [main] o.e.j.w.c.WebSocketClient:196 - Started org.eclipse.jetty.websocket.client.WebSocketClient@179d4544
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.c.AbstractLifeCycle:177 - STARTED org.eclipse.jetty.websocket.client.WebSocketClient@179d4544
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.w.c.WebSocketClient:136 - connect websocket:com.hospitality.hp.visma.client.WebSocketListener@d69c3e2 to:ws://localhost:9900
2017-06-12 14:23:04 | DEBUG | [main] o.e.j.u.t.QueuedThreadPool:342 - WebSocketClient@396182852{STARTED,8<=8<=200,i=4,q=0} dispatched FutureCallback@4e310d66{true,false,null}
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-11] o.e.j.i.SelectorManager:379 - Queued change org.eclipse.jetty.io.SelectorManager$ManagedSelector$Connect@2bb8ad23
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-10-selector-0] o.e.j.i.SelectorManager:446 - Selector loop woken up from select, 0/0 selected
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-10-selector-0] o.e.j.i.SelectorManager:406 - Running change org.eclipse.jetty.io.SelectorManager$ManagedSelector$Connect@2bb8ad23
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-10-selector-0] o.e.j.i.SelectorManager:443 - Selector loop waiting on select
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-10-selector-0] o.e.j.i.SelectorManager:446 - Selector loop woken up from select, 1/1 selected
2017-06-12 14:23:04 | DEBUG | [WebSocketClient@396182852-10-selector-0] o.e.j.w.c.i.WebSocketClientSelectorManager:56 - Connection Failed
java.net.ConnectException: Connection refused
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
    at org.eclipse.jetty.io.SelectorManager.finishConnect(SelectorManager.java:257)
    at org.eclipse.jetty.io.SelectorManager$ManagedSelector.processConnect(SelectorManager.java:529)
    at org.eclipse.jetty.io.SelectorManager$ManagedSelector.processKey(SelectorManager.java:502)
    at org.eclipse.jetty.io.SelectorManager$ManagedSelector.select(SelectorManager.java:455)
    at org.eclipse.jetty.io.SelectorManager$ManagedSelector.run(SelectorManager.java:420)
    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:596)
    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:527)
    at java.lang.Thread.run(Thread.java:745)
2017-06-12 14:23:04 | INFO  | [WebSocketClient@396182852-10-selector-0] c.h.h.v.c.WebSocketListener:94 - onWebSocketError:  
java.net.ConnectException: Connection refused
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
    at org.eclipse.jetty.io.SelectorManager.finishConnect(SelectorManager.java:257)
    at org.eclipse.jetty.io.SelectorManager$ManagedSelector.processConnect(SelectorManager.java:529)
    at org.eclipse.jetty.io.SelectorManager$ManagedSelector.processKey(SelectorManager.java:502)
    at org.eclipse.jetty.io.SelectorManager$ManagedSelector.select(SelectorManager.java:455)
    at org.eclipse.jetty.io.SelectorManager$ManagedSelector.run(SelectorManager.java:420)
    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:596)
    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:527)
    at java.lang.Thread.run(Thread.java:745)

Here is my logback.xml file: 这是我的logback.xml文件： 

<?xml version="1.0" encoding="UTF-8"?>
<configuration>

    <appender name="AUDITFILE"
              class="ch.qos.logback.core.rolling.RollingFileAppender">
        <file>logs/visma-websocket-client.log</file>
        <append>true</append>
        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
            <fileNamePattern>logs/visma-websocket-client_%d{yyyy-MM-dd}.%i.log
            </fileNamePattern>
            <maxHistory>10</maxHistory>
            <timeBasedFileNamingAndTriggeringPolicy
                    class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
                <maxFileSize>20MB</maxFileSize>

            </timeBasedFileNamingAndTriggeringPolicy>
        </rollingPolicy>
        <encoder>
            <pattern>%date %msg%n
            </pattern>
        </encoder>
    </appender>

    <root level="DEBUG">
         <appender-ref ref="AUDITFILE" />
    </root>

</configuration>

Can someone give me hint how i can reduce this unused logging as it creating a lot of disk space when program is running. 有人可以提示我如何减少未使用的日志记录，因为它在程序运行时会创建大量磁盘空间。 I am wondering is it possible to enable disable this jetty log from application or by adding some parameter in logback.xml file 我想知道是否可以从应用程序中禁用此码头日志，或者通过在logback.xml文件中添加一些参数来启用它

3 个解决方案

解决方案1
 3  2017-10-03 08:52:46

If you want to completely disable just the logs from jetty you can add the following line: 如果您只想完全禁用码头的日志，则可以添加以下行： 

<configuration>
...
    <logger name="org.eclipse.jetty" level="OFF" />
....
</configuration>

You can also change it to ERROR if you want just the error level messages. 如果只需要错误级别消息，也可以将其更改为ERROR 。

Increasing the <root level="DEBUG"> to a higher level will affect the whole application and aslo the logs from jetty. 将<root level="DEBUG">增加到更高的级别将影响整个应用程序，并影响码头的日志。

解决方案2
 0  2017-10-03 08:49:51

<root level="INFO">
         <appender-ref ref="AUDITFILE" />
</root>

This should work. 这应该工作。 You can further increase the level in your xml file to WARN, ERROR or FATAL. 您可以进一步将xml文件中的级别提高到WARN, ERROR or FATAL.

解决方案3
 0  2017-10-05 22:04:28

All the log statements are printed since the root logger has DEBUG level and is associated with the AUDITFILE appender. 由于根记录器具有DEBUG级别并与AUDITFILE附加程序关联，因此将打印所有日志语句。

You can set different logging levels or appenders based on packages. 您可以根据包设置不同的日志记录级别或附加程序。 In your case, add the following line within the configuration element. 根据您的情况，在配置元素中添加以下行。 

<logger name="org.eclipse.jetty" level="WARN"/>

This will make any log statement from the packages that start as org.eclipse.jetty to use a logging level of WARN. 这将使以org.eclipse.jetty开头的软件包中的任何日志语句都使用WARN的日志记录级别。 Meaning only WARN statements or above will be logged. 这意味着将仅记录WARN或更高版本的语句。 Set the level to "OFF" to disable logging for the package. 将级别设置为“ OFF”以禁用包的日志记录。

In case you would still want the statements but in a different appender then you can do, 如果您仍然希望使用这些语句，但使用其他附加程序，则可以这样做， 

<logger name="org.eclipse.jetty" additivity="false">
    <appender-ref ref="AUDIT_FILE_NEW" />
</logger>

Assume that AUDIT_FILE_NEW is another appender implementation that logs to another file or to console. 假定AUDIT_FILE_NEW是另一个附加程序实现，它记录到另一个文件或控制台。 Here additivity is set to false, so that the statements are logged only to the AUDIT_FILE_NEW appender. 此处可加性设置为false，因此语句仅记录到AUDIT_FILE_NEW附加程序。 In case additivity was not set, then it defaults to true, which means the logger will inherit from the root logger. 如果未设置可加性，则默认为true，这意味着记录器将从根记录器继承。 And the statements will be logged to both AUDIT_FILE and AUDIT_FILE_NEW appenders. 语句将同时记录到AUDIT_FILE和AUDIT_FILE_NEW附加程序。

暂无
暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 如何在码头启用登录？ - How to enable logging in jetty? 如何用maven开始和停止码头 - How to start and stop jetty with maven 如何阻止应用程序日志登录到 Tomcat 中的 catalina.out - How to stop application logs from logging into catalina.out in Tomcat 如何在Jetty服务器中启用电汇记录 - How to enable wire logging in Jetty Server 如何在Jetty 8中添加请求日志记录过滤器？ - How to add a request logging filter in Jetty 8? 如果通过双击运行如何停止码头？ - How to stop jetty if run by double clicking? 如何在Google App Engine中停止Jetty Web服务器 - How to stop Jetty webserver in Google App Engine 如何停止 hibernate 过度登录？ - How to stop hibernate excessive logging? 嵌入式Jetty和复杂日志 - Embedded Jetty and Complex Logging Jetty Http客户端日志记录 - Jetty Http Client logging
相关标签
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM