Highlighted
akedanielsson Absent Member.
Absent Member.
2520 views

OPLOCK issues

Hi.
We found difficulties regarding opportunistic locking in the folloing environment:

Server: SLES10sp3 and OES2sp3. File system NSS. Client: Win XP, client 4.91 sp5. Office version: MS Office XP
This shows certainly when saving an existing word document after editing. Word hangs, and sometimes even the computer freezes.

Fix: 1): OPLOCK support has to be disabled (level 0) or... 2): Turn off file caching in the client settings.

Anobody that has other experiences or fixed it in another way? Pity to have to disable a performance feature like this, or maybe it is of less impact?
Labels (2)
0 Likes
4 Replies
Knowledge Partner
Knowledge Partner

Re: OPLOCK issues

Novell, IMO, has never gotten oplocking to work right, no matter what they say. Just disable it, IMO, if you want reliable file access.
0 Likes
Bob-O-Rama
Visitor.

Re: OPLOCK issues

Both of these features are of limited utility in terms of performance. Unless you have users with shared databases ( e.g. dbase, access ), oplocks is of no importance at all. Client side caching can increase performance, but not for the average cube dweller using Office. Disable both, never look back.

OpLocks do work perfectly, the problem is that the locking is inferred from application read / write activity. And applications do all manner of stupid / strange / unexpected stuff. This leads to that stupid / strange / and unexpected stuff causing expensive locking operations to be carried out on the server.

-- Bob
0 Likes
akedanielsson Absent Member.
Absent Member.

Re: OPLOCK issues

kjhurni;2077321 wrote:
Novell, IMO, has never gotten oplocking to work right, no matter what they say. Just disable it, IMO, if you want reliable file access.


Thanks!
0 Likes
akedanielsson Absent Member.
Absent Member.

Re: OPLOCK issues

Bob-O-Rama;2077375 wrote:
Both of these features are of limited utility in terms of performance. Unless you have users with shared databases ( e.g. dbase, access ), oplocks is of no importance at all. Client side caching can increase performance, but not for the average cube dweller using Office. Disable both, never look back.

OpLocks do work perfectly, the problem is that the locking is inferred from application read / write activity. And applications do all manner of stupid / strange / unexpected stuff. This leads to that stupid / strange / and unexpected stuff causing expensive locking operations to be carried out on the server.

-- Bob


Thanks!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.