FINER TRACE 400 Use for messages that provide detailed information about the running state of an application. Log messages of TRACE are usually

Size: px

Start display at page:

Download "FINER TRACE 400 Use for messages that provide detailed information about the running state of an application. Log messages of TRACE are usually"

气赔易
5 years ago
Views:

1 JEAP 6.x Logging Subsystem 簡介及相關 Tips JEAP 6.x 在架構上與 JEAP 4.x 和 5.x 有很大的差異, 以 Logging 機制來說,JEAP 6.x 內建的 Logging Framework 包含 JBoss Logging Apache Commons Logging Apache log4j Simple Logging Facade for Java (SLF4J) 和 Java SE Logging, 您可選擇使用 JEAP 6.x 內建的 Logging 機制, 或使用應用程式內的這些 Library 來產出 Log, 但會需要做一些額外的設定, 才能讓系統運作正常, 您可參考 Migration Guide 裡的內容, 或請參考以下概略說明 [ 預設的 Log 檔案存放位置 ] Standalone Mode Domain Mode Log 檔案名稱與存放路徑 EAP_HOME/standalone/log/server.log EAP_HOME/domain/log/host-controll er.log EAP_HOME/domain/log/process-cont roller.log EAP_HOME/domain/servers/SERVERN AME/log/server.log 官方說明 Server Log. Contains all server log messages, including server startup messages. Host Controller boot log. Contains log messages related to the startup of the host controller. Process controller boot log. Contains log messages related to the startup of the process controller. The server log for the named server. Contains all log messages for that server, including server startup messages. [JEAP 6.x 支援的 Log Level] JEAP 6.x 支援最常見的六個 Log Level, 從低到高的順序為 :TRACE DEBUG INFO WARN ERROR 和 FATAL 可用 Log Level 來限制 Log Category 和 Log Handler 要處理哪些層級的 Log JEAP 6.x 支援的 Log Level 如下表所列 Log Level Value 官方說明 FINEST Page 1 of 8

2 FINER TRACE 400 Use for messages that provide detailed information about the running state of an application. Log messages of TRACE are usually only captured when debugging an application. DEBUG 500 Use for messages that indicate the progress individual requests or activities of an application. Log messages of DEBUG are usually only captured when debugging an application. FINE CONFIG INFO 800 Use for messages that indicate the overall progress of the application. Often used for application startup, shutdown and other major lifecycle events. WARN 900 Use to indicate a situation that is not in error but is not considered ideal. May indicate circumstances that may lead to errors in the future. WARNING ERROR 1000 Use to indicate an error that has occurred that could prevent the current activity or request from completing but will not prevent the application from running. SEVERE FATAL 1100 Use to indicate events that could cause critical service failure and application shutdown and possibly cause JBoss EAP 6 to shutdown. 可透過 Management Console 來變更 Log Level( 如下圖 ) Page 2 of 8

3 圖 1 [Log Category] 可用 Log Category 來設定哪些 Class 產出的 Log 的 Log Level, 及要使用哪個 Log Handler 來處理這些 Log, 舉例 <logger category="org.sample" use-parent-handlers="false"> <level name="debug"/> <handlers> <handler name="sample_appender1"/> </handlers> </logger> [Root Logger] Root Logger 是 Supper Logger, 會抓取所有傳送到 Server 的特定 Log Level 的 Log, 然後將這些 Log 交給指定的 Log Handler 來處理以下為 JEAP 6.x 預設的 Root Logger 設定 <root-logger> <level name="info"/> <handlers> Page 3 of 8

4 <handler name="console"/> <handler name="file"/> </handlers> </root-logger> [Log Handler] 可用 Log Handler 來指定要如何紀錄 JEAP 捕捉到的 Log,JEAP 6.x 內建的 Log Handler 如下表所列類別官方說明 Console Console log handlers write log messages to either the host operating system's standard out (stdout) or standard error (stderr) stream. These messages are displayed when JBoss EAP 6 is run from a command line prompt. The messages from a Console log handler are not saved unless the operating system is configured to capture the standard out or standard error stream. File File log handlers are the simplest log handlers that write log messages to a specified file. Periodic Periodic log handlers write log messages to a named file until a specified period of time has elapsed. Once the time period has passed then the file is renamed by appending the specified timestamp and the handler continues to write into a newly created log file with the original name. Size Size log handlers write log messages to a named file until the file reaches a specified size. When the file reaches a specified size, it is renamed with a numeric prefix and the handler continues to write into a newly created log file with the original name. Each size log handler must specify the maximum number of files to be kept in this fashion. Async Async log handlers are wrapper log handlers that provide asynchronous behavior for one or more other log handlers. These are useful for log handlers that may have high latency or other performance problems such as writing a log file to a network file system. Custom Custom log handlers enable to you to configure new Page 4 of 8

5 syslog types of log handlers that have been implemented. A custom handler must be implemented as a Java class that extends java.util.logging.handler and be contained in a module. Syslog-handlers can be used to send messages to a remote logging server. This allows multiple applications to send their log messages to the same server, where they can all be parsed together. 舉例 <periodic-rotating-file-handler name="file" autoflush="true"> <formatter> <named-formatter name="pattern"/> </formatter> <file relative-to="jboss.server.log.dir" path="server.log"/> <suffix value=".yyyy-mm-dd"/> <append value="true"/> </periodic-rotating-file-handler> 若 JEAP 6.x 內建的 Log Handler 沒有符合您需要的, 可嘗試用 Custom Handler 來設定, 例如 : 想要讓 JEAP 6.x Server Log 依照日期再依照大小切檔, 若您的 JEAP 版本是 6.3 以下 ( 包含 6.3), 可用 Custom Handler 來設定,CLI 指令範例如下設定 custom-handler /profile=full/subsystem=logging/custom-handler=periodic-size-rotating-file-handler:add(class =org.jboss.logmanager.handlers.periodicsizerotatingfilehandler, module=org.jboss.logmanager, formatter="%d{hh:mm:ss,sss} %-5p [%c] (%t) %s%e%n", properties={append=true,rotatesize=2048,maxbackupindex=20,suffix=".yyyy-mm-dd",filenam e="${jboss.server.log.dir}/server.log"}) 在 root-logger 新增 periodic-size-rotating-file-handler /profile=full/subsystem=logging/root-logger=root:add-handler(name=periodic-size-rotating -file-handler) 以這個範例來說, 是需重啟 Server 的 [Log Formatter] Page 5 of 8

6 可用 Log Format 來制定 Log 的格式, 格式為基於 java.util.formatter 語法的字串, 若設定如下圖 2 Log 訊息會像這樣圖 3 支援的格式化語法如下表所列語法官方說明 %c The category of the logging event %p The level of the log entry (info/debug/etc) %P The localized level of the log entry %d The current date/time (yyyy-mm-dd HH:mm:ss,SSS form) %r The relative time (milliseconds since the log was initialized) %z The time zone %k A log resource key (used for localization of log messages) %m The log message (including exception trace) %s The simple log message (no exception trace) %e The exception stack trace (no extended module information) %E The exception stack trace (with extended module information) %t The name of the current thread Page 6 of 8

7 %n A newline character %C The class of the code calling the log method (slow) %F The filename of the class calling the log method (slow) %l The source location of the code calling the log method (slow) %L The line number of the code calling the log method (slow) %M The method of the code calling the log method (slow) %x The Nested Diagnostic Context %X The Message Diagnostic Context %% A literal percent character (escaping) [ 如何使用 JEAP 6.x 內建的 Logging 機制 ] 可參考以下步驟來使用 JEAP 6.x 內建的 Logging 機制 1. 應用程式不需要包 Log4j library(jar), 也不需要包設定 Log4j 的設定檔案 (properties 或 xml) 2. 程式必須 import org.jboss.logging.logger 定義寫 log 的 logger 名稱, 舉例 package com.mpinfo.test.servlet; import org.jboss.logging.logger; public class JEAP6TestLog extends HttpServlet { private Logger logger = Logger.getLogger("mpinfo"); ( 略 ) 3. 在 JEAP 設定 Log Handler 與 Log Category( 用甚麼方式紀錄 Log 檔案名稱與路徑 Log 格式等 ),CLI 指令範例如下 /profile=full/subsystem=logging/file-handler=applog/:add(name=applog,file={"path"=>"c:\\testlog\ \ap2.log"},encoding=utf-8,level=debug,autoflush=true,append=true) /profile=full/subsystem=logging/logger=mpinfo:add(level=debug,handlers=[applog],use-parent-han dlers=false [ 如何使用應用程式內的 Log4j 來產生 Log] Page 7 of 8

8 此處是針對 Log4j 來討論, 若程式內有使用 JEAP 6.x 內建的其他 Logging Framework( 如 Apache Commons Logging 或 SLF4J 等 ), 設定方式是不一樣的, 若您有疑問或碰到困難, 請尋求專業的 JAVA 顧問來協助您以下為 JEAP 6.3 以上版本 ( 包含 6.3) 的設定方式, 若版本為較低, 建議您升級, 或請參考內的說明 1. 應用程式需把 Log4j 的 library 和設定檔包進 war 或 ear 內 2. 在 JEAP 設定 Log Handler 與 Log Category( 用甚麼方式紀錄 Log 檔案名稱與路徑 Log 格式等 ),CLI 指令範例如下 /profile=full/subsystem=logging:write-attribute(name=add-logging-api-dependencie s, value=false) 3. 於 JEAP 啟動參數加上以下參數 -Dorg.jboss.as.logging.per-deployment=false 4. 重新啟動 JEAP 5. 佈署應用程式希望以上的概略說明, 能讓您更了解 JEAP 6.x 的 Logging 機制, 若有疑問或碰到困難, 請尋求專業的 JAVA 顧問來協助您 Page 8 of 8

epub83-1

epub83-1 C++Builder 1 C + + B u i l d e r C + + B u i l d e r C + + B u i l d e r C + + B u i l d e r 1.1 1.1.1 1-1 1. 1-1 1 2. 1-1 2 A c c e s s P a r a d o x Visual FoxPro 3. / C / S 2 C + + B u i l d e r / C