ppkarwasz commented on issue #3706:
URL:
https://github.com/apache/logging-log4j2/issues/3706#issuecomment-2933838484
Hi @verjan-isencia,
Thank you for reporting this issue.
This appears to be a composite problem caused by two factors:
1. In version `2.23.0`, we introduced support for Disruptor 4, while still
maintaining compatibility with Disruptor 3—the last major version that supports
our Java 8 baseline. However, the tool we use to generate the OSGi manifest
assumes by default that only one major version of each dependency is supported.
As a result, we forgot to explicitly override this and set the supported
version range for Disruptor to `[3.4,5)`. This will be corrected in #3707.
2. To work around breaking changes in Disruptor 4, we use reflection to load
the appropriate class for the detected version:
https://github.com/apache/logging-log4j2/blob/49cdf7457eab03df3cc09d9419bb4f40c173dbc8/log4j-core/src/main/java/org/apache/logging/log4j/core/async/DisruptorUtil.java#L53-L54
Unfortunately, this detection fails in your environment and incorrectly
identifies your Disruptor version as 4.x. We have not been able to reproduce
this issue in our PAX Exam 4 tests with either Equinox or Felix.
Could you please provide more details about your OSGi environment? A minimal
reproducible example would be especially helpful.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
