Skip to content
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

ShardingJDBC is not supported p6spy driver,add p6spy driver support to ShardingJDBC infra #31782

Closed
lcjing opened this issue Jun 20, 2024 · 1 comment · Fixed by #31814
Closed

Comments

@lcjing
Copy link
Contributor

lcjing commented Jun 20, 2024

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.0

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

ShardingSphere-JDBC

Expected behavior

can normal connection to the database

Actual behavior

org.apache.shardingsphere.infra.database.core.exception.UnsupportedStorageTypeException: Unsupported storage type of URL 'jdbc:p6spy:mysql://xxx:3306?autoReconnect=true&useUnicode=true&characterEncoding=UTF-8'.

Reason analyze (If you can)

ShadingJDBC jbdcUrl prefix not supproted jdbc:p6spy:mysql://

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).

dataSources:
  db_test:
    dataSourceClassName: org.apache.tomcat.jdbc.pool.DataSource
    driverClassName: com.p6spy.engine.spy.P6SpyDriver
    url: jdbc:p6spy:mysql://xxx:3306?autoReconnect=true&useUnicode=true&characterEncoding=UTF-8
    username: u_dev
    password: xxx
@lcjing
Copy link
Contributor Author

lcjing commented Jun 20, 2024

please assign to me

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