EnvironmentConfig.addDataDir no longer has any effect?

Question

I've been using various berkeleydb versions for almost a decade and a half with the same configuration in the DatabaseEnvironment setup:
        EnvironmentConfig config = new EnvironmentConfig();
        File dataDirectory = new File(baseDirectory, "data");
        dataDirectory.mkdirs();
        config.addDataDir(dataDirectory);
        File logDirectory = new File(baseDirectory, "log");
        logDirectory.mkdirs();
        config.setLogDirectory(logDirectory);
        oldLogDirectory = new File(baseDirectory, "oldlog");
        oldLogDirectory.mkdirs();
        File tmpDirectory = new File(baseDirectory, "tmp");
        tmpDirectory.mkdirs();
        config.setTemporaryDirectory(tmpDirectory.getPath());
Suddenly, after a recent switch to version 6.1 of berkeleydb, the addDataDir call seems to be having no effect. Instead, all the database files get created in the baseDirectory. Oddly the log files are still going in the log subdirectory, old log files in oldlog, etc. Just data files seem affected. Weirder, if I use an existing database, it finds them, but new databases I create *since* the change go in the wrong directory. This seems simple as can be, so I don't see how I can suddenly be screwing this up after 14 years. When I examine the result of getDataDirs upon creating the tables it has the single directory I set it to. But it is clearly ignoring it for NEWLY created tables. So why is this suddenly happening?

Answer 1

KDZ is correct!  setDataDir is deprecated.  Replacement calls are addDataDir and setCreateDir.  The java version of the doc is not as clear as it could be and we will correct that.   A better description is found in the C doc.
thanks
mike