jboss实战之一 ----jboss日志

JBOSS日志:
1、涉及到的配置文件和日志文件:server/XXX/conf/jboss-log4j.xml server/XXX/log/server.log
2、jboss日志默认包括控制台日志(对应jboss-log4j.xml配置文件中的 <appender name="CONSOLE" )和文件日志(对应jboss-log4j.xml配置文件中的 <appender name="FILE" )。默认情况下,jboss采用DailyRollingFileAppender(每天循环生成)方式生成文件日志:server.log,每次启动jboss时生成的日志都会覆盖上次启动时生成的日志。


3、如何更改文件日志生成的位置?

默认情况下,文件日志的生成位置在 JBOSS-HOME/server/default/log 目录下,通过设置参数jboss.server.log.dir的值可以更改文件日志生成的位置,如:Djboss.server.log.dir=C:/Logs/JBossLog。在什么地方设置呢?由于此参数值在jboss启动后已经确定,所以我们应该在启动的时候设置此参数值.

 1) 打开启动文件run.bat,在其中增加一行:set JAVA_OPTS=-Djboss.server.log.dir=C:/Logs/JBossLog %JAVA_OPTS%,注意:在%JAVA_OPTS%前有一个空格。

 2) 运行run.bat,启动jboss,启动完成后可以看到在C:/Logs/JBossLog 目录下生成了server.log日志文件。

 


4、每次启动jboss时,如何使生成的日志不覆盖上次的日志?

 在jboss-log4j.xml文件中改变name为file的appender的append参数值为true。

 

如此设置之后,隔天生成的日志仍然会覆盖前面的日志(如9月2日生成的日志会覆盖9月1日生成的日志),如何使之不覆盖呢?只需在jboss-log4j.xml文件中改变name为file的appender的class属性值为:org.jboss.logging.appender.RollingFileAppender

5、如何控制jboss生成的日志量?

在开发过程或者生产环境中,会生成大量的日志,这些日志可能会占用大量的磁盘空间。我们可以通过设置日志级别来控制生成的日志量。比如,使用hibernate时,会生成大量如下类似日志:


为了减少此类日志的生成,我们可以在jboss-log4j.xml文件中增加一个category:

<category name="org.hibernate">
<priority value="INFO"/>
</category>

其中name的值为你想要减少的日志的开头部分。上面的配置为:把org.hibernate开头的日志级别设置为info,这样debug级别的日志将不会输出。

  • 0
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
The JBoss 5 Application Server is a Java Enterprise Edition 5 application server that provides services that most enterprise applications need, such as security, transactionality, persistence, monitoring, resource management, and remote access. JBoss 5 Application Server is compliant with the specification defined by the Java Community Process. JBoss in Action teaches readers how to use the JBoss application server, digging into the things that separate JBoss from other Java EE servers. This book goes deeply into the advanced features and configuration of the server. In particular, it focuses on enterprise-class topics, such as high availability, security, and performance. The book walks you through the JBoss 5 Application Server, from installation and configuration to production deployment. It guides you through configuring the server’s component containers, such as the JBoss Web Server, the EJB3 server, and JBoss Messaging. It also gives you detailed insight into configuring the services, such as security, performance, and clustering. Beyond coverage of the core application server, the book also teaches you how to use some of the “hot” technologies that run on top of the application server, such as JBoss Seam and JBoss Portal. The authors, both seasoned professional experts at developing and administering JBoss, provide meaningful explanations and background on many topics, all tied together with practical, real-world advice from their collective experience. The uniquely comprehensive explanations and the overall wide coverage provided in this book surpass any other content currently available. This book is perfect for developers writing Java EE applications, as well as administrators responsible for maintaining the JBoss Application Server.
deploy/jbossweb-tomcat55.sar/server.xml <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve" prefix="access_log." suffix=".log" pattern="%h %t %r %s %D" directory="${jboss.server.home.dir}/../output/logs" resolveHosts="false" /> http://tomcat.apache.org/tomcat-5.5-doc/config/valve.html pattern配置: %a - Remote IP address %A - Local IP address %b - Bytes sent, excluding HTTP headers, or '-' if zero %B - Bytes sent, excluding HTTP headers %h - Remote host name (or IP address if resolveHosts is false) %H - Request protocol %l - Remote logical username from identd (always returns '-') %m - Request method (GET, POST, etc.) %p - Local port on which this request was received %q - Query string (prepended with a '?' if it exists) %r - First line of the request (method and request URI) %s - HTTP status code of the response %S - User session ID %t - Date and time, in Common Log Format %u - Remote user that was authenticated (if any), else '-' %U - Requested URL path %v - Local server name %D - Time taken to process the request, in millis %T - Time taken to process the request, in seconds %I - current request thread name (can compare later with stacktraces) There is also support to write information from the cookie, incoming header, outgoing response headers, the Session or something else in the ServletRequest. It is modeled after the apache syntax: %{xxx}i for incoming request headers %{xxx}o for outgoing response headers %{xxx}c for a specific request cookie %{xxx}r xxx is an attribute in the ServletRequest %{xxx}s xxx is an attribute in the HttpSession The shorthand pattern name common (which is also the default) corresponds to '%h %l %u %t "%r" %s %b'.
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

登峰大数据

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值