logback 1.1.3 發布,Java開源日志組件
Logback是由log4j創始人設計的又一個開 源日志組件。logback當前分成三個模塊:logback-core,logback- classic和logback-access。logback-core是其它兩個模塊的基礎模塊。logback-classic是log4j的一個 改良版本。此外logback-classic完整實現SLF4J API使你可以很方便地更換成其它日志系統如log4j或JDK14 Logging。logback-access訪問模塊與Servlet容器集成提供通過Http來訪問日志的功能。
logback 1.1.3 發布,此版本更新內容如下:-
Fixed
</li>FileAppender
's prudent mode so that it properly recovers from IO Errors (LOGBACK-1046) -
Irrelevant or internal stack trace lines can now be omitted. (LOGBACK-540).
</li> -
</li>AccessEvent
now creates a copy of request attributes when itsprepareForDeferredProcessing()
method is called. (LOGBACK-1033) -
All threads opened by
</li>ch.qos.logback.core.util.ExecutorServiceUtil#THREAD_FACTORY
are now daemons, which fixes an application hang on shutdown whenLoggerContext#stop()
is not called (LOGBACK-929). -
Fixed an issue with
</li>RollingFileAppender
where the first rollover file could be unintentionally deleted, depending on the specified filename pattern (LOGBACK-894). -
Fixed an issue with
</li>TeeHttpServletResponse
where the system default encoding would be used instead of the response encoding when constructing a new writer (LOGBACK-1023). -
Fixed
</li>ConfigurationDelegate.groovy
to allow any appender that implementsAppenderAttachable
, which supports third-party appenders, such as reactor-logback'sAsyncAppender
(LOGBACK-1008) -
Added support for specifying the callstack depth range in the
</li>PatternLayout
. For example,%caller{1..2}
displays the first two calls in the callstack. -
Added HTTP request method to
</li>MDCInsertingServletFilter
. -
Fixed time-zone dependent code in
</li>RollingCalendarTest
. (LOGBACK-116) -
Simplified connection logic of SocketApender to reduce multi-threading overhead and unnecessary instantiation of
</li>SocketConnector
objects. -
Fixed race condition in
</li>SMTPAppenderBase
causing missing or duplicate emails. (LOGBACK-909) -
Fixed an issue with
</li>FileAppender
in prudent mode, where an interrupt could prevent further access to the file (LOGBACK-875). -
Fixed
</li>IllegalStateException
when multiple threads write files to same directory (LOGBACK-128). -
Changed queue consumption strategy in
</li>AbstractSocketAppender
from "take" to "peek/remove" in order to avoid losing an event on each socket connection break. Zero is now a deprecated queue size. A queue size of one should be taken instead to indicate synchronous processing. (LOGBACK-977) -
</li>RequestLogImpl
now has an overridableconfigure
method to allow extending implementations to configure it via methods other than thelogback-access.xml
file. -
Fixed a bug in
</li>AccessEvent
which could cause anyAsyncAppender
based appender to corrupt the request headers, request parameters, or response headers, before logging. -
SQL scripts to setup your logback database are now provided as JAR resources (LOGBACK-948).
</li> -
Threads created internally by logback are now named logback-n, where n is an integer. For the first thread n is set to 1, for each successive thread n is incremented by 1.
</li> -
Added max runtime parameter to
</li>AsyncAppender
to allow the appender to flush events, up to a maximum delay, during a stop of the LoggerContext. This can be used to ensure that all queued events are flushed. -
Added new configuration element
</li>shutdownHook
to allow the user to specify a ShutdownHook implementation that will stop the Logback context upon JVM exit. -
</li>BasicStatusManager
now prevents adding more than one instance ofOnConsoleStatusListener
as a status listener. This fixes LOGBACK-976. -
</li>TimeBasedRollingPolicy
now accepts a time zone in its%d
conversion pattern. (LOGBACK-611) -
It is now possible to configure the character encoding used by
</li> </ul>SyslogAppender
to encode messages using thesetCharset()
method. This fixes LOGBACK-732請注意:
所有 logback 模塊要求 JDK 1.6,而不是 JDK 1.5!
此版本現已提供下載:
- </li>
-
</li>
</ul>
來自:http://www.oschina.net/news/60972/logback-1-1-3
本文由用戶 cd33 自行上傳分享,僅供網友學習交流。所有權歸原作者,若您的權利被侵害,請聯系管理員。轉載本站原創文章,請注明出處,并保留原始鏈接、圖片水印。本站是一個以用戶分享為主的開源技術平臺,歡迎各類分享!