[logback-dev] [JIRA] Commented: (LBCLASSIC-273) Status messages of StatusManager are not cleared upon call to LoggerContext.reset()

[Joern Huxhorn (JIRA)]

    [ http://jira.qos.ch/browse/LBCLASSIC-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12133#action_12133 ] 

Joern Huxhorn commented on LBCLASSIC-273:
-----------------------------------------

I just realized that the above changes are indeed not sufficient for our use-cases since we also have places in our code that are solely checking for logging configuration errors without performing a prior reset(). We don't have any information about the threshold, i.e. the time of the last configuration, in that case since reconfiguration and evaluation are in separate parts of the code.
There is also no way to retrieve this information from the context, mainly caused by the fact that ContextBase.reset() is not resetting the birthTime.

Beside that, my previous comments still apply.

> Status messages of StatusManager are not cleared upon call to LoggerContext.reset()
> -----------------------------------------------------------------------------------
>
>                 Key: LBCLASSIC-273
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-273
>             Project: logback-classic
>          Issue Type: Bug
>    Affects Versions: 0.9.28
>            Reporter: Joern Huxhorn
>            Assignee: Logback dev list
>
> See https://github.com/ceki/logback/pull/15

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