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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

5461.0. "Unable to lock window table property" by GIDDAY::CHONG (Andrew Chong - Sydney CSC ) Wed Aug 11 1993 00:41


	When looking into domains , sometimes an error message window
pops up with message : Unable to lock window table property
A customer has seen this message a number of times and wants to know the
significance of this message ? and ways to avid it . Iconic map is unlock
at the time. 


andrew
	
T.RTitleUserPersonal
Name
DateLines
5461.1anyone knows the answer ....GIDDAY::CHONGAndrew Chong - Sydney CSC Thu Aug 12 1993 20:3711
    
    
    Re: .0 
    
    	Can someone please tell me what the message means , it is not 
    in the messages manual . 
    
    	I know everyone is very busy and I really appreciate if a few
    minutes could be spared to answer this. 
    
    Andrew
5461.2re:.0TOOK::LEMMONMon Aug 16 1993 14:0421
    Each Iconic Map invocation stores information about itself (e.g., maps
    open, severity info, etc...) in a global window table residing in the
    X-server.   
    
    Access to the window table must be exclusive.  If not, one thread
    (in the same process or a different iconic map process) can write to
    the table while another is reading it!    To avoid this the iconic map
    creates an X-property, the window table lock, and attempts to lock it
    (via XtGetselectionOwner).  It tries 25 times.  If it can't lock it,
    you get the error message you are seeing.  
    
    Usually there are no bad side affects it the window table isn't
    updated.    This entire mechanism is not public so if your customer
    isn't using the pm-pm communications s/he should be ok.
    
    Does your customer always get this error message?   If so, is it
    reproducable?   
    
    /Jim
    
    p.s. please send reply to took::lemmon