null lock? problem (AREV Specific)
At 08 JUL 1999 12:47:42PM Victor Engel wrote:
We have just run into an interesting problem. There is a lock that seems to belong to everyone. No matter who runs NLM_STATS and checks the locks on table CHANGES, the program reports the logged user owns the lock, even if they just did a cold boot. Furthermore, it shows an extra session for that user. In an attempt to resolve this problem, I am having all users log off an restart their workstations. Any idea what is going on? My thinking is that somehow a null user is in the lock table. Suggestions?
At 08 JUL 1999 01:36PM Victor Engel wrote:
This problem was resolved by having all users log off and restart their workstations. Actually, all but two users logged off. This seems to indicate that one of the users had set the "null" lock which got cleared when their workstation was restarted. I still have no idea what the root cause of this problem is.
Perhaps the following will shed some light, though. For a period of time, when I checked the locks on the !CHANGES file (the file that had the problem), one of the locks appeared with nothing listed for the client. Querying the locks repeatedly using NLM_STATS resulted in various values for client, all appearing to be control characters of some sort. Other than that period of time, though, the lock always showed up as belonging to the currently logged user.