堆棧內存溢出
  簡體   English   中英

如何停止碼頭應用程序中的登錄

[英]How to stop logging in jetty application

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

問題描述

我正在使用碼頭實施websocket客戶端。 在應用程序啟動以及重新連接Websocket失敗時，這會在日志文件中產生大量噪音。 實際上，在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)

這是我的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>

有人可以提示我如何減少未使用的日志記錄，因為它在程序運行時會創建大量磁盤空間。 我想知道是否可以從應用程序中禁用此碼頭日志，或者通過在logback.xml文件中添加一些參數來啟用它

3 個解決方案

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

如果您只想完全禁用碼頭的日志，則可以添加以下行： 

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

如果只需要錯誤級別消息，也可以將其更改為ERROR 。

將<root level="DEBUG">增加到更高的級別將影響整個應用程序，並影響碼頭的日志。

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

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

這應該工作。 您可以進一步將xml文件中的級別提高到WARN, ERROR or FATAL.

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

由於根記錄器具有DEBUG級別並與AUDITFILE附加程序關聯，因此將打印所有日志語句。

您可以根據包設置不同的日志記錄級別或附加程序。 根據您的情況，在配置元素中添加以下行。 

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

這將使以org.eclipse.jetty開頭的軟件包中的任何日志語句都使用WARN的日志記錄級別。 這意味着將僅記錄WARN或更高版本的語句。 將級別設置為“ OFF”以禁用包的日志記錄。

如果您仍然希望使用這些語句，但使用其他附加程序，則可以這樣做， 

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

假定AUDIT_FILE_NEW是另一個附加程序實現，它記錄到另一個文件或控制台。 此處可加性設置為false，因此語句僅記錄到AUDIT_FILE_NEW附加程序。 如果未設置可加性，則默認為true，這意味着記錄器將從根記錄器繼承。 語句將同時記錄到AUDIT_FILE和AUDIT_FILE_NEW附加程序。

暫無
暫無

聲明:本站的技術帖子網頁，遵循CC BY-SA 4.0協議，如果您需要轉載，請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

相關問題 如何在碼頭啟用登錄？ 如何用maven開始和停止碼頭 如何阻止應用程序日志登錄到 Tomcat 中的 catalina.out 如何在Jetty服務器中啟用電匯記錄 如何在Jetty 8中添加請求日志記錄過濾器？ 如果通過雙擊運行如何停止碼頭？ 如何在Google App Engine中停止Jetty Web服務器 如何停止 hibernate 過度登錄？ 嵌入式Jetty和復雜日志 Jetty Http客戶端日志記錄
相關標簽
 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM