Re: Potential Bug in Log4j2?
Ralph Goers <[email protected]>
| Newsgroups | gmane.comp.jakarta.log4j.user |
|---|---|
| Message-ID | <[email protected]> |
Please create a Jira issue for this with as much information as you can. Thanks, Ralph > On Dec 16, 2021, at 5:01 PM, Bhavesh Patel <[email protected]> wrote: > > Hi Matt/Anyone, Any solution for this? > Regards,Bhavesh. > On Thursday, December 16, 2021, 01:57:23 PM PST, Bhavesh Patel <[email protected]> wrote: > > HI, As a part of this commit, https://github.com/apache/logging-log4j2/commit/97db5743a3b10e9017bf70794d6275b21553dd44, the thread leak issue was fixed. But did it introduce a bug? What if the KafkaAppender is stopped? In the calls hierarchy, the KafkaManager.stop() is called. This in turn calls KakfaManager.releaseSub() which calls KafakManager.closeProducer(). The closeProducer() closes the producer. Now when you try to start the KafkaAppender and append a message using KafkaAppender.append() the following message is seen > "Cannot perform operation after producer has been closed". > Please let me know if you see this as a bug. > Regards,Bhavesh. > > > > > > >