Skip to content

ClassNotFoundException for CLASS BASED sharding algorithm in Quarkus framework #35552

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zhfeng opened this issue May 29, 2025 · 0 comments · May be fixed by #35553
Open

ClassNotFoundException for CLASS BASED sharding algorithm in Quarkus framework #35552

zhfeng opened this issue May 29, 2025 · 0 comments · May be fixed by #35553

Comments

@zhfeng
Copy link
Contributor

zhfeng commented May 29, 2025

Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Which version of ShardingSphere did you use?

5.5.1

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-JDBC

Expected behavior

It can load the custome algorithm class.

Actual behavior

It throws CNFE.

Reason analyze (If you can)

It is related to with ClassBasedShardingAlgorithmFactory
and there are multi class loaders in Quarkus framework. We need to try with TCCL.

The similar issue is like

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

Example codes for reproduce this issue (such as a github link).

@zhfeng zhfeng linked a pull request May 29, 2025 that will close this issue
7 tasks
zhfeng added a commit to zhfeng/sharding-sphere that referenced this issue May 29, 2025
zhfeng added a commit to zhfeng/sharding-sphere that referenced this issue May 29, 2025
@linghengqian linghengqian added this to the 5.5.3 milestone May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants