Opening another env handle while other operations are in progress

Question

Dear community!
1. When I am performing some long operations on a container, I also open another env handle for the same environment in the different process. Then the opening of the second handle crashes the application. Am I allowed to do so, or just I misconfigured my environment?
This is my configuration code.
EnvironmentConfig envConf = new EnvironmentConfig();
envConf.setAllowCreate(true); // If the environment does not
// exits, create it.
envConf.setInitializeCache(true); // Turn on the shared memory
// region.
envConf.setInitializeLocking(true); // Turn on the locking subsystem.
envConf.setInitializeLogging(true); // Turn on the logging subsystem.
envConf.setTransactional(true);
envConf.setErrorStream(System.out);
envConf.setRegister(true);
envConf.setRunRecovery(true);
log.debug("Opening DB environment at " + envHome.getAbsolutePath());
Environment tntEnv = new Environment(envHome, envConf);
2. And the second question. Does EnvironmentConfig object affect Environment itself, in other words can I use differently configured EnvironmentConfig objects when opening environment at the same time (in multiprocess applications)?
Thanks in advance
Vyacheslav

Answer 1

Vyacheslav,
(1) what crash do you see? generally speaking Berkeley DB will "join" an existing environment and ignore your current configuration if an environment exists in the directory you specify.
(2) no, you can't do that and if the system doesn't return you an error you will see problems somewhere along the way.
One thing you MUST NOT do is to run recovery in more than one thread. I think that may be your problem. It looks like you are specifying runRecovery(true) in the new environment -- this will certainly crash (or lead to non-deterministic errors) a running application. Recovery may only be run by one thread at a time, with exclusive access to the environment.
Regards,
George