2011-11-07 48 views
6

使用ehCache 2.4.4,我似乎进入了ehCache Segment对象的死锁。从其他日志记录中,我知道'等待线程',1694最后在该堆栈跟踪生成之前9小时运行了任何东西。与此同时,1696年已经做了很多其他的工作,所以这个锁定肯定会被忽略。我该如何解决这个明显的EhCache死锁?

我很自信,我并不直接锁定任何Segment实例,所以我认为这是图书馆内部的某种问题。有任何想法吗?

"Model Executor - 1696" Id=1696 in TIMED_WAITING on lock=java.u[email protected]92eb1ed 
at sun.misc.Unsafe.park(Native Method) 
at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) 
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source) 
at java.util.concurrent.PriorityBlockingQueue.poll(Unknown Source) 
at com.rtrms.application.modeling.local.BlockingTaskList.takeTask(BlockingTaskList.java:20) 
at com.rtrms.application.modeling.local.ModelExecutor.executeNextTask(ModelExecutor.java:71) 
at com.rtrms.application.modeling.local.ModelExecutor.run(ModelExecutor.java:46) 

Locked synchronizers: count = 1 
    - [email protected]3d767f 

"Model Executor - 1694" Id=1694 in WAITING on loc[email protected]4a3d767f 
owned by Model Executor - 1696 Id=1696 
at sun.misc.Unsafe.park(Native Method) 
at java.util.concurrent.locks.LockSupport.park(Unknown Source) 
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(Unknown Source) 
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(Unknown Source) 
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(Unknown Source) 
at java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(Unknown Source) 
at net.sf.ehcache.store.compound.Segment.unretrievedGet(Segment.java:248) 
at net.sf.ehcache.store.compound.CompoundStore.unretrievedGet(CompoundStore.java:191) 
at net.sf.ehcache.store.compound.impl.DiskPersistentStore.containsKeyInMemory(DiskPersistentStore.java:72) 
at net.sf.ehcache.Cache.searchInStoreWithStats(Cache.java:1884) 
at net.sf.ehcache.Cache.get(Cache.java:1549) 
at com.rtrms.amoeba.cache.DistributedModeledSecurities.get(DistributedModeledSecurities.java:57) 
at com.rtrms.amoeba.modeling.AssertPersistedModeledSecurities.get(AssertPersistedModeledSecurities.java:44) 
at com.rtrms.application.modeling.tasks.ExpandableModelingTask.getNextUnexecutedTask(ExpandableModelingTask.java:35) 
at com.rtrms.application.modeling.local.BlockingTaskList.takeTask(BlockingTaskList.java:36) 
at com.rtrms.application.modeling.local.ModelExecutor.executeNextTask(ModelExecutor.java:71) 
at com.rtrms.application.modeling.local.ModelExecutor.run(ModelExecutor.java:46) 

Locked synchronizers: count = 0 
+0

原来,这个问题是无效的。我已经将此文档(http://ehcache.org/documentation/user-guide/jta#performance)解释为指示显式锁不使用基于段的锁定,但事实并非如此。这个死锁是由我的代码引起的,有一个锁定版本不在finally()块中。 – sharakan

+3

如果你已经知道了,为什么你不回答自己的问题,所以它不会出现在未解答的问题中? – xmoex

回答

1

原来,像Cache.acquireWriteLockOnKey呼叫最终获得对内部段的锁,所以这种明显的僵局用.unlock呼叫,这不是在最后一个块引起的。

编辑点评:它也意味着你可以争取试图锁定恰好在同一段中的两个不同的键,这是非常不幸的。

+1

如果确实如此,您可以将此帖标记为答案。只需点击答案左侧的投票计数器下方的大复选标记符号 - 以这种方式表明问题已得到回答:) –