Uploaded image for project: 'logback'
  1. logback
  2. LOGBACK-1167

Filename Patterns remain in context collision map following stop

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.1.6, 1.1.7
    • Fix Version/s: 1.1.9
    • Component/s: logback-core
    • Labels:
      None

      Description

      When using a ch.qos.logback.classic.sift.SiftingAppender, calls to stop on the nested appenders where the timeout has been reached does not remove the filename patterns for those appenders from the collision map (CoreConstants.FA_FILENAME_COLLISION_MAP).

      Later attempts to restart and log to the appender (using the same sifting key/discriminator value) results in a file name collision error.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ceki Ceki Gülcü
                Reporter:
                medgar Michael Edgar
              • Votes:
                3 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: