logback / LOGBACK-1663 [Open] LoggingEvent#sequenceNumber always 0 event after configuring a SequenceNumberGenerator ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1663 ============================== Issue created ------------------------------ Bertrand Renuart created this issue on 18/Aug/22 12:00 AM Summary: LoggingEvent#sequenceNumber always 0 event after configuring a SequenceNumberGenerator Issue Type: Bug Affects Versions: 1.3.0-beta0 Assignee: Logback dev list Components: logback-classic Created: 18/Aug/22 12:00 AM Priority: Major Reporter: Bertrand Renuart Description: The sequence number of logging events remains at 0 (zero) even after configuring a SequenceNumberGenerator in the LoggerContext. I tried to configure a sequence number generator in the logback.xml configuration file as follows: {code:xml} <configuration> <sequenceNumberGenerator class="ch.qos.logback.core.spi.BasicSequenceNumberGenerator"/> ... </configuration> {code} Although this configuration is accepted without error/warning, a call to LoggerContext#getSequenceGenerator() at runtime always returns null. After some investigations it appears that LoggerContext#getSequenceNumber() is *hardcoded to always return _null_* (see [here|http://example.com/]): {code:java} public SequenceNumberGenerator getSequenceNumberGenerator() { return null; } {code} Also {{LoggerContext}} extends {{ContextBase}} which also maintains a reference to a SequenceNumberGenerator together with the associated setter and getter methods. Looks like there is some confusion about which class should own the generator... ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)