bigseafish900711 opened a new issue, #7606: URL: https://github.com/apache/incubator-seata/issues/7606
### Check Ahead - [x] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. - [x] I am willing to try to fix this bug myself. ### Ⅰ. Issue Description store: # support: file 、 db 、 redis 、 raft mode: db db: datasource: druid db-type: mysql driver-class-name: com.mysql.jdbc.Driver url: jdbc:mysql://**:3306/seata?rewriteBatchedStatements=true user: seata password: seata min-conn: 10 max-conn: 100 global-table: global_table branch-table: branch_table lock-table: lock_table distributed-lock-table: distributed_lock vgroup-table: vgroup_table query-limit: 1000 max-wait: 5000 这个是配置文件 我已经把mysql-connector-j-8.4.3.jar 复制到/seata-server/libs和/seata-server/libs/jdbc中了。 同时也复制到/lib和/lib/jdbc中了。 但是还是会提示 Caused by: org.apache.seata.common.loader.EnhancedServiceNotFoundException: not found service provider for : org.apache.seata.core.store.db.DataSourceProvider caused by java.lang.IllegalStateException: Extension instance(definition: org.apache.seata.common.loader.ExtensionDefinition@ddde9df5, class: interface org.apache.seata.core.store.db.DataSourceProvider) could not be instantiated: The driver {com.mysql.jdbc.Driver} cannot be found in the path /lib/jdbc/. Please ensure that the appropriate database driver dependencies are included in the classpath 下面是我运行的脚本 docker run -d -p 8091:8091 -p 7091:7091 -e SEATA_IP=127.0.0.1 -v /www/server/seata/config/mysql-connector-j-8.4.3.jar:/lib/mysql-connector-j-8.4.3.jar --name seata apache/seata-server:2.1.0.jre17 我也参考了如下的 https://github.com/apache/incubator-seata/issues/6760 但就是无法解决。 ### Ⅱ. Describe what happened <img width="1339" height="690" alt="Image" src="https://github.com/user-attachments/assets/1cceeb40-38ce-4b39-b8e0-9569a4872364"; /> <img width="1324" height="639" alt="Image" src="https://github.com/user-attachments/assets/d11bbf2b-c896-4cb0-8d47-809fbe1339e3"; /> ### Ⅲ. Describe what you expected to happen 理论上应该是可以运行成功的 ### Ⅳ. How to reproduce it (as minimally and precisely as possible) _No response_ ### Ⅴ. Anything else we need to know? _No response_ ### Ⅵ. Environment _No response_ -- 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...@seata.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org For additional commands, e-mail: notifications-h...@seata.apache.org
