JBossCache-1.2.4 with Hibernate-3.1.2, IdentityLock ERROR lo
jaikiran Mar 3, 2006 4:51 AMHi,
We *were* using Hibernate-2.1.3 and JBossCache-1.2 with JBoss-3.2.3. Because of PESSIMISTIC locking issues, we are in the process of upgrading to Hibernate-3.1.2 and JBossCache-1.2.4(we are still using PESSIMISTIC approach). We are currently seeing a lot of logs as below:
15:14:05,296 WARN [LRUAlgorithm] eviction timed out. Will retry later.
15:14:06,796 ERROR [IdentityLock] write lock for /com/dbdata/core/hibernateobject/SmSegmentPlanRelationship/smParentSegments/com.dbdata.core.hibernateobject.SmSegmentPlanRelationship.smParentSegments#com.dbdata.core.hibernateobject.SmSegmentPlanRelationshipId[segmentPlanId=56203, segmentPlanVersionId=1, relationshipId=6] could not be acquired a
fter 1500 ms. Locks: Read lock owners: {GlobalTransaction:<null>:357=java.lang.Object@b2e5d0}
Write lock owner: null
(caller=Thread[Thread-35,5,jboss], lock info: read owners=[GlobalTransaction:<null>:357] (activeReaders=1, activeWriter=null, waitingReaders=0, waitingWriters=0, waitingUpgrader=0))
15:14:06,796 WARN [LRUAlgorithm] eviction timed out. Will retry later.
15:14:08,296 ERROR [IdentityLock] write lock for /com/dbdata/core/hibernateobject/SmSegmentPlanRelationship/smPickBestQualifications/com.dbdata.core.hibernateobject.SmSegmentPlanRelationship.smPickBestQualifications#com.dbdata.core.hibernateobject.SmSegmentPlanRelationshipId[segmentPlanId=56203, segmentPlanVersionId=1, relationshipId=5] could n
ot be acquired after 1500 ms. Locks: Read lock owners: {GlobalTransaction:<null>:357=java.lang.Object@b2e5d0}
Write lock owner: null
(caller=Thread[Thread-35,5,jboss], lock info: read owners=[GlobalTransaction:<null>:357] (activeReaders=1, activeWriter=null, waitingReaders=0, waitingWriters=0, waitingUpgrader=0))
15:14:08,296 WARN [LRUAlgorithm] eviction timed out. Will retry later.
15:14:09,796 ERROR [IdentityLock] write lock for /com/dbdata/core/hibernateobject/SmSegmentPlanRelationship/smLogicalSegmentRuns/com.dbdata.core.hibernateobject.SmSegmentPlanRelationship.smLogicalSegmentRuns#com.dbdata.core.hibernateobject.SmSegmentPlanRelationshipId[segmentPlanId=56203, segmentPlanVersionId=1, relationshipId=5] could not be ac
quired after 1500 ms. Locks: Read lock owners: {GlobalTransaction:<null>:357=java.lang.Object@b2e5d0}
Write lock owner: null
(caller=Thread[Thread-35,5,jboss], lock info: read owners=[GlobalTransaction:<null>:357] (activeReaders=1, activeWriter=null, waitingReaders=0, waitingWriters=0, waitingUpgrader=0))
15:14:09,796 WARN [LRUAlgorithm] eviction timed out. Will retry later.
15:14:11,296 ERROR [IdentityLock] write lock for /com/dbdata/core/hibernateobject/SmSegmentPlanRelationship/smChildSegments/com.dbdata.core.hibernateobject.SmSegmentPlanRelationship.smChildSegments#com.dbdata.core.hibernateobject.SmSegmentPlanRelationshipId[segmentPlanId=56203, segmentPlanVersionId=1, relationshipId=5] could not be acquired aft
er 1500 ms. Locks: Read lock owners: {GlobalTransaction:<null>:357=java.lang.Object@b2e5d0}
Write lock owner: null
(caller=Thread[Thread-35,5,jboss], lock info: read owners=[GlobalTransaction:<null>:357] (activeReaders=1, activeWriter=null, waitingReaders=0, waitingWriters=0, waitingUpgrader=0))
15:14:11,311 WARN [LRUAlgorithm] eviction timed out. Will retry later.
15:14:12,811 ERROR [IdentityLock] write lock for /com/dbdata/core/hibernateobject/SmSegmentPlanRelationship/smParentSegments/com.dbdata.core.hibernateobject.SmSegmentPlanRelationship.smParentSegments#com.dbdata.core.hibernateobject.SmSegmentPlanRelationshipId[segmentPlanId=56203, segmentPlanVersionId=1, relationshipId=5] could not be acquired a
fter 1500 ms. Locks: Read lock owners: {GlobalTransaction:<null>:357=java.lang.Object@b2e5d0}
Write lock owner: null
(caller=Thread[Thread-35,5,jboss], lock info: read owners=[GlobalTransaction:<null>:357] (activeReaders=1, activeWriter=null, waitingReaders=0, waitingWriters=0, waitingUpgrader=0))
15:14:12,811 WARN [LRUAlgorithm] eviction timed out. Will retry later.
Our LockAcquisitionTimeout is 1500ms in treecache.xml.
Can these logs be ignored? Or are they indicating any serious issues?
Thank you.