[jboss-jira] [JBoss JIRA] (JBAS-9548) JBoss 5.0 log file is stopped getting updated after a while
Ramesh Kodali (JIRA)
jira-events at lists.jboss.org
Wed Oct 2 14:28:02 EDT 2013
Ramesh Kodali created JBAS-9548:
-----------------------------------
Summary: JBoss 5.0 log file is stopped getting updated after a while
Key: JBAS-9548
URL: https://issues.jboss.org/browse/JBAS-9548
Project: Application Server 3 4 5 and 6
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: JBossAS-5.0.1.GA
Environment: Java 2.6, JBoss 5.1
Reporter: Ramesh Kodali
Assignee: Alessio Soldano
We are using log back xml to configure application specific log file and copied the log back XML in JBoss class path. After server restarts, JBoss is generating the log files successfully. It was working from some time even in production. Recently we have noticed a weird issue in our dev environment that, application logs are writing in to log file and stopped writing after a while. We have to restart the JBoss to get back the Log files status. This issue seems coming continuously now a days. I would like to know is it some thing related to JBoss or more of environment issue.
Here below the log back configuration we had
<appender name="FILE"
class="ch.qos.logback.core.rolling.RollingFileAppender">
<File>${jboss.server.log.dir}/cbs2.log</File>
<Append>true</Append>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<FileNamePattern>${jboss.server.log.dir}/cbs2.%d{yyyy-MM-dd}.%i.log.gz
</FileNamePattern>
<timeBasedFileNamingAndTriggeringPolicy
class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
<maxFileSize>200MB</maxFileSize>
</timeBasedFileNamingAndTriggeringPolicy>
</rollingPolicy>
<layout class="ch.qos.logback.classic.PatternLayout">
<Pattern>%d{yyyy-MM-dd;HH:mm:ss.SSS} [%thread] %-5level %logger{36} [%M:%L]
[%X{id}->%X{bcId}:%X{userId}:%X{loginId}] - %msg%n</Pattern>
</layout>
</appender>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list