One common problem when trying to diagnose DFC configuration problems is determining where exactly your DFC configuration is coming from. The DFC configuration files likg log4j.properties and dfc.properties are located through the classpath. This provides a lot of power for configuring DFC in various different environments (like WAR files and EAR files). It is a double edged sword though. If your classpath is not quite set up right then you can often find the wrong DFC configuration.
There is a system property that you can set to help diagnose these kinds of problems. The property is "dfc.diagnose_config". If you add this system property to the command line of your java invocation then DFC will display the name of the configuration files that it is using.
java -Ddfc.diagnose_config ...
The output will include something like the following:
Reading DFC configuration from "file:/C:/configuration/dfc.properties"
Reading log4j configuration from "file:/C:/configuration/log4j.properties"
Reading dbor configuration from "file:/C:/configuration/dbor.properties"