{"record":{"id":"89f0fd16010b4cd5","repo":"apache/shardingsphere","slug":"setclientinfo-properties","errorCode":null,"errorMessage":"setClientInfo properties","messagePattern":"setClientInfo properties","errorType":"exception","errorClass":"UnsupportedSQLOperationException","httpStatus":null,"severity":"error","filePath":"jdbc/src/main/java/org/apache/shardingsphere/driver/jdbc/unsupported/AbstractUnsupportedOperationConnection.java","lineNumber":134,"sourceCode":"    \n    @Override\n    public final Properties getClientInfo() throws SQLException {\n        throw new SQLFeatureNotSupportedException(\"getClientInfo\");\n    }\n    \n    @Override\n    public final String getClientInfo(final String name) throws SQLException {\n        throw new SQLFeatureNotSupportedException(\"getClientInfo name\");\n    }\n    \n    @Override\n    public final void setClientInfo(final String name, final String value) {\n        throw new UnsupportedSQLOperationException(\"setClientInfo name value\");\n    }\n    \n    @Override\n    public final void setClientInfo(final Properties props) {\n        throw new UnsupportedSQLOperationException(\"setClientInfo properties\");\n    }\n}\n","sourceCodeStart":116,"sourceCodeEnd":137,"githubUrl":"https://github.com/apache/shardingsphere/blob/e952770a215630a3659c75d64369168cd3e26b82/jdbc/src/main/java/org/apache/shardingsphere/driver/jdbc/unsupported/AbstractUnsupportedOperationConnection.java#L116-L137","documentation":"ShardingSphere's JDBC driver does not implement the java.sql.Connection method setClientInfo properties (bulk-setting JDBC 4 client info properties on the connection). The abstract base class AbstractUnsupportedOperationConnection, which ShardingSphereConnection extends, overrides it as final and unconditionally throws SQLFeatureNotSupportedException. ShardingSphere deliberately rejects client-info mutation with UnsupportedSQLOperationException, so the Properties-based setter always throws. The exception is thrown the moment the method is invoked on any connection produced by the ShardingSphere Driver.","triggerScenarios":"Calling Connection.setClientInfo(properties) with a non-empty Properties object on a ShardingSphere connection.","commonSituations":"Framework/pool startup code that copies client info onto every new connection; monitoring agents applying a property bundle after checkout; migrations from drivers that accept these properties.","solutions":["Drop the bulk setClientInfo call for ShardingSphere connections, or guard it with a catch of SQLFeatureNotSupportedException.","Encode the equivalent settings in each storage unit's JDBC URL inside the ShardingSphere configuration.","Iterate unwrap(connection) per backend and apply properties there if backend-level state is required."],"exampleFix":null,"handlingStrategy":"try-catch","validationCode":"boolean supportsOp = false;\ntry {\n    connection.getMetaData(); // connection is alive\n    // JDBC has no capability flag for individual methods; probe once per JVM:\n    supportsOp = probeSupport(connection); // reflective/one-time guarded call\n} catch (final SQLException ignored) {\n}\n// Simpler and recommended: capability-check by driver URL\nboolean isShardingSphere = url.startsWith(\"jdbc:shardingsphere:\");\nif (isShardingSphere) {\n    // skip the unsupported call, use the alternative API path\n}","typeGuard":null,"tryCatchPattern":"try {\n    connection.setClientInfo(/* args */);\n} catch (final SQLFeatureNotSupportedException e) {\n    // expected on ShardingSphere connections: fall back to supported API\n    log.debug(\"Driver does not support setClientInfo properties, using fallback\", e);\n}","preventionTips":["Bulk client-info application at pool checkout must be guarded by a driver check; encode equivalent properties in storage-unit JDBC URLs instead.","Check the JDBC URL before calling optional JDBC 4 methods: connections starting with jdbc:shardingsphere: never support the lob/network-timeout/client-info/callable APIs.","Catch java.sql.SQLFeatureNotSupportedException (parent of ShardingSphere's UnsupportedSQLOperationException) around optional driver-capability calls so the application degrades gracefully."],"tags":["jdbc","shardingsphere","unsupported-operation","connection-api"],"backgroundTag":null,"analyzedSha":"e952770a215630a3659c75d64369168cd3e26b82","analyzedAt":"2026-08-14T13:54:53.392Z","schemaVersion":2},"datasetVersion":"2026-08-15T22:17:37.221Z"}