terrymanu commented on issue #38317:
URL:
https://github.com/apache/shardingsphere/issues/38317#issuecomment-3991397886
This is not a ShardingSphere core logic bug; it is a packaging/runtime
dependency issue.
When the release is built with the `all` profile, optional SPI modules are
included in the distribution
(e.g., `shardingsphere-transaction-base-seata-at`), but Seata’s full
runtime dependencies are not bundled automatically.
Once Seata-related SPI is loaded at startup or during SQL execution, it
can fail with
`NoClassDefFoundError: org/apache/seata/...`.
There are two ways to resolve it:
1. If Seata is required:
Manually add Seata client dependencies (`seata-all` and related
transitive dependencies)
to the Proxy runtime classpath (typically `ext-lib`).
2. If Seata is not required:
Remove the Seata module (`shardingsphere-transaction-base-seata-at`)
from the distribution,
or rebuild with a packaging profile that does not include that optional
module.
Conclusion: this is a distribution composition/dependency management
issue, not a defect in transaction kernel behavior.
--
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]
