terrymanu commented on issue #37845:
URL:
https://github.com/apache/shardingsphere/issues/37845#issuecomment-3799248753
Problem Understanding
- ShardingSphere-JDBC 5.5.1 with Oracle master (oracle) and slave
(oracle-read) via Druid. Enabling Druid PSCache on the master
(pool-prepared-statements=true,
max-pool-prepared-statement-per-connection-size=20) makes startup fail;
removing it or enabling only on the slave succeeds. Read/Write splitting rules
and single-table rule are configured via Java API.
Root Cause
- Not enough evidence to call this a ShardingSphere bug. ShardingSphere
reuses externally provided DataSources and does not alter Druid PSCache
behavior. A connection failure triggered solely by Druid PSCache likely
originates in the Druid/Oracle driver layer during datasource init or first
connection retrieval; need the actual exception to confirm.
Analysis
- Official docs (5.5.x readwrite-splitting Java API) show
ShardingSphereDataSourceFactory expects ready-made DataSources; it does not
parse or enforce Druid PSCache settings.
- Only the master has PSCache enabled; routing still reaches the master,
so the failure point is the oracle datasource initialization/connection.
Without the stack trace we cannot see whether it is a precompiled statement
cache, validation query, or Oracle driver cursor limit issue.
- No logs, datasource config details, or direct Druid-only test results
were provided, so we cannot separate datasource misconfiguration from a
potential integration issue.
Conclusion / Info Needed
- Cannot conclude a ShardingSphere bug. Please provide:
1. Full stack trace when master PSCache is enabled (include root cause
message and error codes).
2. Full master and slave Druid configs (driver class, validation
query, filters, etc.) to confirm PSCache is the only difference.
3. Result of initializing the same master DruidDataSource without
ShardingSphere and calling getConnection().
4. Oracle server version and JDBC driver version.
With these details we can determine if the issue is in datasource
settings or ShardingSphere integration.
--
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]
