[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::pwv50ift

Title:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Notice:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Moderator:CPEEDY::KENNEDY
Created:Fri Dec 18 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4319
Total number of notes:18478

4152.0. "lk lock: resourse lock deadlock on <pwrk$shr>" by GIDDAY::COOK (Matt Cook , CSC Sydney Australia) Tue Feb 11 1997 19:31

	
	G'day All,

		I have a customer who has just installed PW v5.0e the install all went fine and the server 
	appears to be working fine , however the customer noticed the following error in the 
	PWRK$LMMCP_node.LOG 

	lk lock: resourse lock deadlock on <pwrk$shr>

	does anybody know what this error is ???

	
	Thanks,

	Matt Cook
T.RTitleUserPersonal
Name
DateLines
4152.1UTRTSC::SWEEPI want a lolly...Wed Feb 12 1997 03:206
    I don't think that this is an error. You stumbled onto a deadlock
    and the code retries. So if you only see 1 of these messages then
    it is just an info. msg. If you see large nr's of them, then you
    have a problem.
    
    Adrie
4152.2VMSNET::P_NUNEZWed Feb 12 1997 14:2214
    
    How 'bout this set:
    
    12-FEB-1997 10:48:44.83 20E002B3:029954E0 LKLock: resource lock
    deadlock on <PWRK$SHR>
    12-FEB-1997 10:48:56.29 20E002B3:029E11E0 LKunlock: attmpet to release
    un-held resource lock <PWRK$SHR>
    
    Note, the misspelled "attmpet" is not mine. 
    
    Note the time stamps on these two - I don't think the 2 are related.
    
    Paul
    
4152.3UTRTSC::SWEEPI want a lolly...Thu Feb 13 1997 03:469
    No again its not a big deal. 
    The typo is indeed in the code
         ERROR((_lg, "LKunlock: attmpet to release un-held resource lock
    <%s>\n",
    
    There were some optimizations made in the code to reduce
    the nr of locks. You might have hit a tiny bug, but its not fatal.
    
    Adrie