[logback-dev] [JIRA] Issue Comment Edited: (LBCORE-106) TimeBasedRollingPolicy append logs into a old log file, instead of rolling the log file.

Ceki Gulcu (JIRA) noreply-jira at qos.ch
Tue Jul 7 22:49:10 CEST 2009


    [ http://jira.qos.ch/browse/LBCORE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11221#action_11221 ] 

Ceki Gulcu edited comment on LBCORE-106 at 7/7/09 10:48 PM:
------------------------------------------------------------

I was hoping that this issue was a duplicate of LBCORE-94. However, looking at your config file, it is not. (Your RollingFileAppenders set the File property.)

I can't reproduce this problem. However, if you set a status listener, for example by defining  -Dlogback.statusListenerClass=SYSOUT, you should have logback print its internal status on the console as it attempts to archive log files which should shed some light on this matter. 

You could also write a small servlet which prints the status data. There is an example in [1]. 

Once you obtain the status manager, you can iterate through the status messages. To obtain the status manage:
    LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory();
    StatusManager sm = lc.getStatusManager();

You could also view status information via JMX. After you install the jmxConfigurator (by just adding <jmxConfigurator /> to your logback.xml file, start jconsole, and visit the mbean under "ch.qos.logback.classic". 

In any case, I need to see the status data before going forward.

[1] http://svn.qos.ch/viewvc/logback-demo/trunk/src/main/java/ch/qos/logback/demo/statii/


      was (Author: noreply.ceki at qos.ch):
    I was hoping that this issue was a duplicate of LBCORE-94. However, looking at your config file, it is not. (Your RollingFileAppenders set the File property.)

I can't reproduce this problem. However, if you set a status listener, for example by defining  -Dlogback.statusListenerClass=SYSOUT, you should have logback print its internal status on the console as it attempts to archive log files which should shed some light on this matter. 

You could also write a small servlet which prints the status data. There is an example in [1]. 

Once you obtain the status manager, you can iterate through the status messages. To obtain the status manage:
    LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory();
    StatusManager sm = lc.getStatusManager();

In any case, I need to see the status data before going forward.

[1] http://svn.qos.ch/viewvc/logback-demo/trunk/src/main/java/ch/qos/logback/demo/statii/

  
> TimeBasedRollingPolicy append logs into a old log file, instead of rolling the log file.
> ----------------------------------------------------------------------------------------
>
>                 Key: LBCORE-106
>                 URL: http://jira.qos.ch/browse/LBCORE-106
>             Project: logback-core
>          Issue Type: Bug
>          Components: Appender
>    Affects Versions: 0.9.15
>         Environment: Linux, Sun JDK 5
>            Reporter: Ralph Goers
>            Assignee: Ceki Gulcu
>         Attachments: logback.xml
>
>
> It appears that LBCORE-26 was not completely fixed. I have users who seem the be having the same problem. The text below is the relevant portion of the email I received from them.
> There is same issue today also. Yesterday the nova1a-qa and nova1b-qa servers were restarted and after that the system logged the info to the server.log and server_mc.log files.
> Today the system logs most info to the server.2009-07-06.log and server_mc.2009-07-06.log files and some info to the server.log and server_mc.log files.
>  
> Below is example from the nova1a-qa:/opt/jboss/sbfw-V2.0.0-onlineserv-home/server/default/log
>  
> [akma4116 at nova1a-qa:/opt/jboss/sbfw-V2.0.0-onlineserv-home/server/default/log]$                                                                              ls -ltr
>  
> ...
>  
> -rw-rw-r--  1 jboss jboss   327312 Jul  5 23:50 server.2009-07-05.log
> -rw-rw-r--  1 jboss jboss   327312 Jul  5 23:50 server_mc.2009-07-05.log
> -rw-rw-r--  1 jboss jboss     6384 Jul  5 23:58 jboss.log.2009-07-05
> -rw-rw-r--  1 jboss jboss   250839 Jul  6 13:20 server_07_06_09_14_34_54.log
> -rw-rw-r--  1 jboss jboss   347440 Jul  6 13:20 server_mc_07_06_09_14_34_54.log
> -rw-rw-r--  1 jboss jboss   755260 Jul  6 14:18 console_07_06_09_14_34_54.log
> -rw-rw-r--  1 jboss jboss   856101 Jul  6 14:18 server_mc.2009-07-02.log
> -rw-rw-r--  1 jboss jboss   912958 Jul  6 14:18 server.2009-07-02.log
> -rw-rw-r--  1 jboss jboss    87149 Jul  6 14:34 boot.log
> -rw-rw-r--  1 jboss jboss 36091128 Jul  6 23:58 jboss.log.2009-07-06
> -rw-rw-r--  1 jboss jboss   108572 Jul  7 06:30 sbc_ib-exp_HQResponseTime.log
> -rw-rw-r--  1 jboss jboss    12810 Jul  7 07:48 server.log
> -rw-rw-r--  1 jboss jboss    18207 Jul  7 07:48 server_mc.log
> -rw-rw-r--  1 jboss jboss   148904 Jul  7 07:48 console.log
> -rw-rw-r--  1 jboss jboss   424746 Jul  7 08:20 ROOT_HQResponseTime.log
> -rw-rw-r--  1 jboss jboss   374460 Jul  7 08:25 hyperic-hq_HQResponseTime.log
> -rw-rw-r--  1 jboss jboss   231082 Jul  7 08:40 server_mc.2009-07-06.log
> -rw-rw-r--  1 jboss jboss   241730 Jul  7 08:40 server.2009-07-06.log
> -rw-rw-r--  1 jboss jboss    17574 Jul  7 08:42 sbc_mc-exp_HQResponseTime.log
> -rw-rw-r--  1 jboss jboss   556062 Jul  7 08:46 jboss.log
> [akma4116 at nova1a-qa:/opt/jboss/sbfw-V2.0.0-onlineserv-home/server/default/log]$ tail -f server.2009-07-06.log                                                08:40:00.018 [DefaultQuartzScheduler_Worker-4] DEBUG c.i.s.c.s.UpdateOnlinePayrollUserStatusJob [->:] - Exiting getAllPendingIOPUsers.
> 08:40:00.018 [DefaultQuartzScheduler_Worker-4] INFO  c.i.s.c.s.UpdateOnlinePayrollUserStatusJob [->:] - There were no Online Payroll users found in memory to sync and update.
> 08:40:00.018 [DefaultQuartzScheduler_Worker-4] DEBUG c.i.s.c.s.UpdateOnlinePayrollUserStatusJob [->:] - Exiting syncUsers.
> 08:40:00.018 [DefaultQuartzScheduler_Worker-3] DEBUG c.i.s.c.s.UpdateBillingManagerUserStatusJob [->:] - Entering getAllActiveBMUsers.
> 08:40:00.018 [DefaultQuartzScheduler_Worker-3] DEBUG c.i.s.c.s.UpdateBillingManagerUserMap [->:] - Entering isEmpty.
> 08:40:00.018 [DefaultQuartzScheduler_Worker-3] DEBUG c.i.s.c.s.UpdateBillingManagerUserMap [->:] - User Map is empty: true
> 08:40:00.018 [DefaultQuartzScheduler_Worker-3] DEBUG c.i.s.c.s.UpdateBillingManagerUserMap [->:] - Exiting isEmpty.
> 08:40:00.018 [DefaultQuartzScheduler_Worker-3] DEBUG c.i.s.c.s.UpdateBillingManagerUserStatusJob [->:] - Exiting getAllActiveBMUsers.
> 08:40:00.019 [DefaultQuartzScheduler_Worker-3] INFO  c.i.s.c.s.UpdateBillingManagerUserStatusJob [->:] - There were no Billing Manager users found in memory to sync and update.
> 08:40:00.019 [DefaultQuartzScheduler_Worker-3] DEBUG c.i.s.c.s.UpdateBillingManagerUserStatusJob [->:] - Exiting syncUsers.
> ò
> [akma4116 at nova1a-qa:/opt/jboss/sbfw-V2.0.0-onlineserv-home/server/default/log]$ tail -f server.log
> 07:47:43.812 [Thread-30] DEBUG c.d.s.i.dao.slave.broker.Response [->00070:root] - Reading response input stream HEADER portion.
> 07:47:43.813 [Thread-29] DEBUG c.d.s.i.d.s.client.DIISBrokerAccess [->00070:root] -
>  
> Received DIIS response:
> DIISMessage{messageContent=<RSP>LOGMESSAGE<RC>0<OK>  ---LOGGED entry  OK---<TMHOST>19, messageId=00000000, validateHeader=true, isValidHeader=true}
>  
>  
> 07:47:43.813 [Thread-29] DEBUG c.d.s.i.dao.slave.diis.DIISLexer [->00070:root] - instantiated DIISLexer
> 07:47:43.813 [Thread-29] DEBUG c.d.s.i.dao.slave.diis.DIISParser [->00070:root] - constructor
> 07:47:43.813 [Thread-29] DEBUG c.d.s.i.logging.IAALogHandler [->00070:root] - Successfully published to the IAALog
>  
> ò
> [akma4116 at nova1a-qa:/opt/jboss/sbfw-V2.0.0-onlineserv-home/server/default/log]$ tail -f server.2009-07-06.log
> 08:50:00.098 [DefaultQuartzScheduler_Worker-4] DEBUG c.i.s.c.s.UpdateOnlinePayrollUserStatusJob [->:] - Exiting getAllPendingIOPUsers.
> 08:50:00.098 [DefaultQuartzScheduler_Worker-4] INFO  c.i.s.c.s.UpdateOnlinePayrollUserStatusJob [->:] - There were no Online Payroll users found in memory to sync and update.
> 08:50:00.098 [DefaultQuartzScheduler_Worker-3] DEBUG c.i.s.c.s.UpdateBillingManagerUserStatusJob [->:] - Entering getAllActiveBMUsers.
> 08:50:00.098 [DefaultQuartzScheduler_Worker-4] DEBUG c.i.s.c.s.UpdateOnlinePayrollUserStatusJob [->:] - Exiting syncUsers.
> 08:50:00.098 [DefaultQuartzScheduler_Worker-3] DEBUG c.i.s.c.s.UpdateBillingManagerUserMap [->:] - Entering isEmpty.
> 08:50:00.098 [DefaultQuartzScheduler_Worker-3] DEBUG c.i.s.c.s.UpdateBillingManagerUserMap [->:] - User Map is empty: true
> 08:50:00.098 [DefaultQuartzScheduler_Worker-3] DEBUG c.i.s.c.s.UpdateBillingManagerUserMap [->:] - Exiting isEmpty.
> 08:50:00.098 [DefaultQuartzScheduler_Worker-3] DEBUG c.i.s.c.s.UpdateBillingManagerUserStatusJob [->:] - Exiting getAllActiveBMUsers.
> 08:50:00.098 [DefaultQuartzScheduler_Worker-3] INFO  c.i.s.c.s.UpdateBillingManagerUserStatusJob [->:] - There were no Billing Manager users found in memory to sync and update.
> 08:50:00.099 [DefaultQuartzScheduler_Worker-3] DEBUG c.i.s.c.s.UpdateBillingManagerUserStatusJob [->:] - Exiting syncUsers.
>  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       


More information about the logback-dev mailing list