Berkeley DB Family

Hi,

I have seen documentation and other posts related to this error
"com.sleepycat.je.EnvironmentLockedException: (JE 4.0.103) The environment cannot be locked for single writer access. ENV_LOCKED: The je.lck file could not be locked. Environment is invalid and must be closed.
at com.sleepycat.je.log.FileManager.<init>(FileManager.java:350)
at com.sleepycat.je.dbi.EnvironmentImpl.<init>(EnvironmentImpl.java:439)
at com.sleepycat.je.dbi.EnvironmentImpl.<init>(EnvironmentImpl.java:341)
"

I used to get this error in the past when I try to connect to the same store from mulitple applications. But I am now certain that I have no processes connected to it, but I still get the same error when I try to start the process. Is there anything (for example, killing a process with out a smooth connection closing) cause this?

I am able to rename the message store folder etc , just to make sure no one else is accessing it. So not sure how the store ended up in a state where no one can connect to it. Are there any lock files that I could delete from the store (with out deleting the actual data) which could recover from this situation.

This is happening in a dev environment, I am worried this occurring in prod is just a matter of time.

Thanks.