Jdbcconfig stores the LoggingInfo config object.
However, at start-up, the database is not yet available. Because of that, the logging.xml from the DD is initially used as a fall-back. Jdbcconfig will reload the logging info later, but only if the the logging config differs from the one in the DD. So far, so good.
If we are also using jdbcstore - in combination with jdbcconfig - jdbcconfig will read the logging info from the store db rather than the file system to compare the difference. But that is not the one that was loaded - the one of the file system was. It doesn't make much sense logically, and furthermore: We basically need the same info three times, in three different locations rather than the necessary two.