slf4j-dev

Download

slf4j-dev@qos.ch

November 2021

1 participants
2 discussions

[JIRA] Updates for SLF4J-525: slf4j-api initialization should be thread safe
by QOS.CH (JIRA) 26 Nov '21

26 Nov '21

SLF4J / SLF4J-525 [Open] slf4j-api initialization should be thread safe ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-525 ============================== 1 comment ------------------------------ Ceki Gülcü on 26/Nov/21 12:48 PM The attached images are very small and blurry. Please provide readable images or alternatively text. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-525: slf4j-api initialization should be thread safe
by QOS.CH (JIRA) 26 Nov '21

26 Nov '21

SLF4J / SLF4J-525 [Open] slf4j-api initialization should be thread safe ============================== 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/SLF4J-525 ============================== Issue created ------------------------------ weipan created this issue on 26/Nov/21 4:09 AM Summary: slf4j-api initialization should be thread safe Issue Type: Bug Affects Versions: 1.7.32 Assignee: SLF4J developers list Attachments: image-2021-11-26-11-02-07-612.png, image-2021-11-26-11-02-41-800.png, image-2021-11-26-11-03-21-460.png, image-2021-11-26-11-04-34-942.png, image-2021-11-26-11-05-35-839.png, image-2021-11-26-11-08-38-968.png Created: 26/Nov/21 4:09 AM Environment: centos8_aarch64 Priority: Major Reporter: weipan Description: when I mvn test in slf4j(a)1.7.32,it happened: !image-2021-11-26-11-02-07-612.png|thumbnail! !image-2021-11-26-11-02-41-800.png|thumbnail! !image-2021-11-26-11-03-21-460.png|thumbnail! I want to know what happens in this function: !image-2021-11-26-11-04-34-942.png|thumbnail! It returns a value of eventCount.get(), which is shown above as 2305 (not fixed) but later as 2275 and passed to the recordedEventCount variable. The expectedEventCount variable is directly determined by the eventCount.get() and extraLogEvents() functions. The return value of extraLogEvents() is 0. Therefore, expectedEventCount is directly transferred by the eventCount.get() function and returns 2305. The final result is 2305 < = 2275 + 16. The key information is why eventCount.get() changes. Check the log code related to eventCount.get()： !image-2021-11-26-11-05-35-839.png|thumbnail! The value of expectedEventCount must be smaller than the value of recordedEventCount+LENIENCY_COUNT, which indicates the tolerance value. That is, the tolerance value range should be extended. However, the initialization should be thread-safe. As a result, the tolerance value range is limited. As a result, an error is reported.So if I can change it this way: !image-2021-11-26-11-08-38-968.png|thumbnail! ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0