Configuration properties cannot be bound to DruidDataSource when the environment contains a non-enumerable property source

[iQiFengLe]

Configuration properties cannot be bound to DruidDataSource when the environment contains a non-enumerable property source

[wilkinsona]

This is quite similar to #38514 which the underlying cause being the same non-enumerable property source that comes from JNDI being available. You can work around the problem by adding a spring.properties file to src/main/resources that contains spring.jndi.ignore=true.

The failure's occurring because DruidDataSource isn't entirely compatible with configuration property binding.

When all property sources are enumerable, binding can be optimised to only try to bind properties that are present in the environment. For example, if there are no spring.datasource.log.connection.* properties in the environment, the binder will never need to call getConnection() on the DruidDataSource.

When there's a non-enumerable property source in the environment, the binder does not know all of the properties that are available so it has to try to bind everything. As part of trying to bind everything, the binder's calling getConnection() so that it can then introspect its result for setter methods and determine which properties need to be bound to it. This call fails as it's happening before the URL had been set. Even if the URL had been set, the call would still be unwanted as it would leak a connection.

Hopefully the workaround above is enough to get you past the problem. I'll leave this open for now as I'm not sure what, if anything, we can do to address it. One option would be to provide a way to indicate properties that should be ignored when binding to a third-party class. Another would be for you to bind properties to a safe class of your own and then use Boot's PropertyMapper to apply those to the DruidDataSource instance. Lastly, you could explore binding properties to Boot's DataSourceProperties class and then building the DataSource from those properties:

 properties.initializeDataSourceBuilder().type(DruidDataSource.class).build();

[quaff]

I know it's risky, but can we ignore JndiPropertySource by default since it's vulnerable and not much useful in practice?

[quaff]

I requested Spring Framework team to disable JndiPropertySource by default. see spring-projects/spring-framework#18598 (comment)

[philwebb]

We've opened #39932 to deal with the Jetty JNDI issue. Once that has been done this issue is effectively a duplicate of #34616