关于BDB内存数据库的异常问题，求大神解答啊

2015-10-02 05:17:31 398 阅读 AI 写同款 · GEO 优化AI 选题数据监测一键分发 ›

Windows SAM文件提取与哈希解密实战：从原理到攻防在Windows系统安全领域，身份认证机制是核心防线。系统通过存储密码的哈希值而非明文来验证用户，其中NTLM哈希是关键的凭证形式。理解其原理对于安全加固与渗透测试至关重要，它直接关系到横向移动等攻击路径的可行性。在实战中，获取存储这些哈希的SAM文件是常见需求，但系统运行时对其有严格的保护机制。因此，利用PE环境并修改文件属性成为突破保护、提取文件的有效方法。掌握从SAM文件中提取哈希，并运用字典、掩码等策略进行解密的技巧，是安全研究人员与系统管理员进行漏洞评估、应急响应与防御加固的必备技能。本文围绕“p 阅读详情

网上关于BDB数据库的资料好少，现在开发个项目，静态数据需要存在BDB数据库，我之前没弄过BDB，在测试BDB查询数据时报错，（具体代码我就不发了，毕竟太多了，而且关联甚密，）出现了以下异常，请问大家这个异常是啥意思？一般怎么修改？

com.sleepycat.je.EnvironmentLockedException: (JE 5.0.103) E:\原型系统\CMCC\CMCC\BDBEnvHome 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:369)

	at com.sleepycat.je.dbi.EnvironmentImpl.<init>(EnvironmentImpl.java:482)

	at com.sleepycat.je.dbi.EnvironmentImpl.<init>(EnvironmentImpl.java:408)

	at com.sleepycat.je.dbi.DbEnvPool.getEnvironment(DbEnvPool.java:178)

	at com.sleepycat.je.Environment.makeEnvironmentImpl(Environment.java:252)

	at com.sleepycat.je.Environment.<init>(Environment.java:233)

	at com.sleepycat.je.Environment.<init>(Environment.java:177)

	at com.ocs.dao.impl.BDBEnv.setup(BDBEnv.java:49)

	at com.ocs.dao.impl.PackageDAOBDBImpl.<init>(PackageDAOBDBImpl.java:49)

	at com.ocs.dao.impl.PackageDAOBDBImpl.getInstance(PackageDAOBDBImpl.java:41)

	at BDB.BDBTest3.setUp(BDBTest3.java:36)

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

	at java.lang.reflect.Method.invoke(Method.java:601)

	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)

	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)

	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)

	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)

	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)

	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)

	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)

	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)

	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)

	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)

	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)

	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)

	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)

	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)

	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)

	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)

	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)

	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)

	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)