Hello, I encountered a potential issue related to java.sql.DriverManager#isDriverAllowed.
In my project, I use multiple custom class loaders derived from the system class loader. They are isolated from each other. One of my class loaders (let’s call it A) is complete, while another class loader (say B) only has a JDBC driver class in its resource directory, but lacks some of its dependencies. When DriverManager#isDriverAllowed checks the driver, this situation can lead to a LinkageError, which in turn prevents obtaining a database connection. I think this behavior could potentially be optimized. If the community agrees, I’d be happy to submit a PR to address this issue. Thanks, shenfeng
