[JIRA] Created: (LBCORE-72) StatusListener not getting notified after a certian period of time
StatusListener not getting notified after a certian period of time ------------------------------------------------------------------ Key: LBCORE-72 URL: http://jira.qos.ch/browse/LBCORE-72 Project: logback-core Issue Type: Bug Affects Versions: 0.9.11 Reporter: Szel Zoltan Assignee: Logback dev list Hi, we have a long running application which uses Logback for logging and we have a status listener installed. During runtime the underlying machine went out of disk space which generated a bunch of errors in our file appender. After cleaning up some disk space we have noticed, that our status listener is not getting notified anymore. Going through the code i have found, that the status listeners are notified only, if the BasicStatusManager contains less then 200 Status messages. Could you please change the code to notify the status listeners before the "max size reached" check happens in the Status Manager? Thanks in advance, Kind Regards, Zoltan Szel -- 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
[ http://jira.qos.ch/browse/LBCORE-72?page=com.atlassian.jira.plugin.system.is... ] Ceki Gulcu resolved LBCORE-72. ------------------------------ Fix Version/s: 0.9.12 Resolution: Fixed Thank you for this report. Issue is resolved in trunk.
StatusListener not getting notified after a certian period of time ------------------------------------------------------------------
Key: LBCORE-72 URL: http://jira.qos.ch/browse/LBCORE-72 Project: logback-core Issue Type: Bug Affects Versions: 0.9.11 Reporter: Szel Zoltan Assignee: Logback dev list Fix For: 0.9.12
Hi, we have a long running application which uses Logback for logging and we have a status listener installed. During runtime the underlying machine went out of disk space which generated a bunch of errors in our file appender. After cleaning up some disk space we have noticed, that our status listener is not getting notified anymore. Going through the code i have found, that the status listeners are notified only, if the BasicStatusManager contains less then 200 Status messages. Could you please change the code to notify the status listeners before the "max size reached" check happens in the Status Manager? Thanks in advance, Kind Regards, Zoltan Szel
-- 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
[ http://jira.qos.ch/browse/LBCORE-72?page=com.atlassian.jira.plugin.system.is... ] Ceki Gulcu closed LBCORE-72. ----------------------------
StatusListener not getting notified after a certian period of time ------------------------------------------------------------------
Key: LBCORE-72 URL: http://jira.qos.ch/browse/LBCORE-72 Project: logback-core Issue Type: Bug Affects Versions: 0.9.11 Reporter: Szel Zoltan Assignee: Logback dev list Fix For: 0.9.12
Hi, we have a long running application which uses Logback for logging and we have a status listener installed. During runtime the underlying machine went out of disk space which generated a bunch of errors in our file appender. After cleaning up some disk space we have noticed, that our status listener is not getting notified anymore. Going through the code i have found, that the status listeners are notified only, if the BasicStatusManager contains less then 200 Status messages. Could you please change the code to notify the status listeners before the "max size reached" check happens in the Status Manager? Thanks in advance, Kind Regards, Zoltan Szel
-- 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
participants (2)
-
Ceki Gulcu (JIRA) -
Szel Zoltan (JIRA)