[jbosscache-dev] LockParentForChildInsertRemove and PessimisticLocking

Brian Stansberry brian.stansberry at redhat.com
Wed Aug 5 13:05:07 EDT 2009


Brian Stansberry wrote:
> Manik Surtani wrote:
>> On 5 Aug 2009, at 17:22, Brian Stansberry wrote:
>>
>>> Another detail that may or may not be relevant:
>>>
>>> Note that the failed lock attempt msg is for a "upgrade lock" not a 
>>> "write lock". That indicates IdentityLock already had the caller 
>>> thread listed as a RL owner on the node. Not sure why the thread would 
>>> have a RL on the node.
>> Any of this running within a tx?
>>
> 
> Good question. Most requests involve a GTX; I'll need to figure out why 
> this one doesn't.
> 

IDE tells me DataGravitationCleanupCommand.get/setGlobalTransaction() is 
never called by any code. So it seems these cleanups are outside of any GTX.


-- 
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat


More information about the jbosscache-dev mailing list