We have a fabric cluster with a blueprint datasource bundle exported as an OSGI Service. The configuration pid for the profile is marked with an update-policy of "reload".

When we edit a datasource property (say password) in Fabric (via Hawtio by editing the [configuration pid].properties file, we can see the change propagated successfully when we go to a container with the profile assigned and run the:

config:list "(service.pid={configuration pid})"

But the blueprint bundle does not seem to pick up the change and the old values continue to be used. This seems only to affect this datasource profile. Even explicitly refreshing the profile does not work. If the container is restarted, the change is picked up.

The datasource is using an Oracle ojdbc client using DBCP 1.4 for pooling.