When the DBAdapter loads a driver, it introspects the driver class for specific internal interfaces—some of which may be marked as reserved (i.e., not meant for public or adapter use). Huawei’s JDBC driver (for GaussDB 100/200 or its RDS for MySQL/PG) is robust and high-performing. However, because it implements certain internal JDBC specs differently—or includes proprietary optimizations—the DBAdapter’s introspection logic may trip over methods or classes that it considers “reserved.”
You might see logs like:
-Dweblogic.jdbc.allowUnsafeDriverAccess=true (For WebLogic; adjust for your middleware.) Check the Huawei GaussDB documentation for the recommended driver version for your application server. Often, a patch release (e.g., huawei-gaussdb-jdbc-1.2.3 instead of 1.2.0 ) resolves interface mismatches. 3. Use a Different Connection Pool (Most Reliable) Bypass DBAdapter entirely by switching to HikariCP, Tomcat JDBC Pool, or Vibur DBCP. Configure your datasource as a “non-JTA” datasource and let the pool handle the Huawei driver directly. dbadapter reserved interface huawei driver
Example with Spring Boot:
Have you encountered a similar issue with another cloud provider’s JDBC driver? Let me know in the comments below. Author bio: [Your Name] – Cloud-native engineer specializing in multi-cloud database connectivity. When the DBAdapter loads a driver, it introspects