[logback-dev] [JIRA] Resolved: (LBCORE-77) When calling the shutdownandreset method of the loggercontext, Status list of the statusmanager is not reset.

[Ceki Gulcu (JIRA)]

     [ http://jira.qos.ch/browse/LBCORE-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ceki Gulcu resolved LBCORE-77.
------------------------------

    Fix Version/s: 0.9.15
       Resolution: Fixed

As for logback 0.9.14, BasicStatusManager's internal buffer is now split into two parts, the header part and the tail part. The header part stores the fist H status messages whereas the tail part stores the last T messages. At present time H=T=150, although these values may change in future releases.

This means that BasicStatusManager will never stop logging. 

However, after reconfiguration it might be helpful to clear the internal buffer of a BasicStatusManager.  To allow this, the clear() method was added to StatutusManager interface in revision 2115.


> When calling the shutdownandreset method of the loggercontext, Status list of the statusmanager is not reset.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: LBCORE-77
>                 URL: http://jira.qos.ch/browse/LBCORE-77
>             Project: logback-core
>          Issue Type: Bug
>    Affects Versions: 0.9.11
>            Reporter: alexis morillo
>            Assignee: Logback dev list
>            Priority: Minor
>             Fix For: 0.9.15
>
>
> To implement the reloading of confifguration, I had to call each time the shutdownandreset followed by the doconfigure. Thought, as the statuslist in BasicStatusManager is not reset at this time,  when it reaches 200 entries, it stops logging, even if the debug mode is true. 

-- 
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