zhanghaou commented on PR #24383: URL: https://github.com/apache/pulsar/pull/24383#issuecomment-3265029864
> > @lhotari > > Java 21.0.8 fixed the bug, it seems Java 21 also affected. > > https://bugs.openjdk.org/browse/JDK-8351933 > > @zhanghaou Thanks for sharing. It looks like it's also fixed in 17.0.17 `apachepulsar/pulsar:4.0.6` contains 21.0.8 so it's addressed there. `apachepulsar/pulsar:3.3.8` also contains Java 21.0.8. `apachepulsar/pulsar:3.0.13` contains 17.0.16 so it's not yet addressed there. It seems that 17.0.17 hasn't been released yet. According to https://wiki.openjdk.org/display/JDKUpdates/JDK+17u, 17.0.17 will be released on October 21, 2025. For Pulsar 3.0.x, it seems that the only workaround is to build a custom docker image that uses Java 21.0.8 to run Pulsar. For users deploying with Docker, this might be helpful. However, many users are likely installing the JDK themselves and running Pulsar directly on a VM. As for the JDK version, it seems we only specify the major version requirement, without detailing the minor versions. The version we maintain internally has removed all dependencies on the ForkJoin Pool, including the content mentioned in this PR, as well as the caffeine part (since asynchronous construction in caffeine also uses the ForkJoinPool by default). Given the current situation, I think this PR is meaningful. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
