gnodet commented on code in PR #26845:
URL: https://github.com/apache/camel/pull/26845#discussion_r4094561226


##########
components/camel-sql/src/main/java/org/apache/camel/component/sql/SqlComponent.java:
##########
@@ -151,6 +158,51 @@ protected Endpoint createEndpoint(String uri, String 
remaining, Map<String, Obje
         return endpoint;
     }
 
+    @Override
+    public void onSecretRotation(Object source) throws Exception {
+        // Collect all DataSources this component can reach: the one injected 
directly (if any)
+        // plus all DataSource beans registered in the registry. The registry 
beans are typically
+        // not recreated during a route reload, so their connection pools 
still hold connections
+        // that were authenticated with the old credentials.
+        Set<DataSource> dataSources = 
getCamelContext().getRegistry().findByType(DataSource.class);
+        if (this.dataSource != null) {
+            dataSources.add(this.dataSource);
+        }
+
+        for (DataSource ds : dataSources) {
+            evictDataSourceConnections(ds, source);
+        }
+    }
+
+    /**
+     * Evicts stale connections from the given DataSource so that the pool 
rebuilds them with the rotated credentials.
+     * <p/>
+     * HikariCP is tried first via reflection (so camel-sql does not need a 
compile-time dependency on it). Any
+     * DataSource that does not expose a {@code softEvictConnections()} method 
is left untouched — the pool will pick up
+     * the new credentials on its own reconnect cycle when existing 
connections expire.
+     */
+    static void evictDataSourceConnections(DataSource ds, Object source) {
+        // HikariCP: softEvictConnections() marks all current connections for 
eviction while
+        // allowing in-flight queries to complete; the pool then recreates 
them with the new credentials.
+        try {
+            Method softEvict = ds.getClass().getMethod("softEvictConnections");

Review Comment:
   Fixed in c1aa008be631090a1f676470aa474fb6489ff319: `softEvictConnections()` 
lives on `HikariPoolMXBean`, not on `HikariDataSource` directly. The fix 
retrieves the MXBean via `getHikariPoolMXBean()` (a public method on 
`HikariDataSource`) using reflection, then calls `softEvictConnections()` on 
the MXBean. Tests updated accordingly to simulate the real two-step indirection.



-- 
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]

Reply via email to