Domino 9 und frühere Versionen > ND6: Entwicklung

Entsperren von Dokumenten

(1/3) > >>

buzzy666:
Tach zusammen,
wir haben ne DB, für die das Sperren von Doks aktiviert ist. Nun kommt es sporadisch vor, dass machen Doks nicht entsperrt werden. Lässt sich nicht an bestimmten Usern festmachen und ist auch nicht reproduzierbar.
Hat jemand ähnliche Erfahrungen gemacht? Ich hab nämlich keinen Bock, stündlich irgendwelchen Leuten nachzutelefonieren, ob sie ein Dok *wirklich* noch in Bearbeitung haben  >:(

Danke & Gruß,
Buzzy

Glombi:
Der Lock-Funktion traue ich nicht über den Weg. Insbesondere vor 6.5.4. kann man die vergessen da zu buggy.

Andreas

Glombi:
In diesem Zusammenhang möchte ich folgendes aus der KBASE zitieren:

What is the Difference Between Soft Locking and Hard Locking in Lotus Notes?

Problem

What is the difference between soft locking and document locking (sometimes called hard locking) and when are these locking features are enabled?


Solution
Document Locking:
In Notes/Domino 6.x, a database property feature called "Allow document locking" was introduced.  When this property is enabled, any user with Author access or above can lock a document across all replicas.  This prevents two or more users from making changes to the same document and then replicating - which would create replication conflict documents.
To enable this feature, you can select the database property "Allow document locking" in the basics tab.
Soft Locking:
Soft locking is also a new feature in Notes/Domino 6, but it was not documented as clearly as document locking.  Soft locks are in-memory locks that are enabled when documents are in memory, and are not persistent.  The editor takes out a soft lock on a document when it is opened, and then unlocks it when the document is closed.  During the period of time when it is soft locked, no one else can edit that document but it only affects the current replica where the user is working; it does not affect other replicas of the database.
Prior to release 6.5.1, soft locks could not be disabled.  Beginning in 6.5.1 and 6.0.4, users can add a NOTES.INI parameter EDIT_NO_SOFT_LOCKS=1 to their client's notes.ini.
The EDIT_NO_SOFT_LOCKS=1 ini parameter was added as a workaround for customers who had applications that did not work well with soft locking. The parameter essentially reverts locking behavior back to the R5 style, where soft locking did not exist. This parameter disables all soft locking in all databases accessed by that client.  It cannot be enabled on a database by database basis.
At this time, there is no other way to disable soft locking.  This parameter can be set programmatically in all clients via LotusScript with the following instructions:

Dim session As New NotesSession
Call session.SetEnvironmentVar( "EDIT_NO_SOFT_LOCKS", "1" , True)
The above script can be included in a Hotspot button included in a mail to all users.
An enhancement request, for soft locking be an option that can be enabled or disabled via a database property like document locking,  has been submitted to Quality Engineering as SPR# JGON5WQLMA.  There are no current plans to address this request.

Andreas

buzzy666:

--- Zitat von: Glombi am 06.12.05 - 09:10:47 ---Der Lock-Funktion traue ich nicht über den Weg. Insbesondere vor 6.5.4. kann man die vergessen da zu buggy.

Andreas

--- Ende Zitat ---

Ich mittlerweile auch nicht mehr - da war ja meine selber programmierte besser  >:(
Ist denn wenigstens dem Softlocking mehr zu trauen, als dem Hardlocking? Weil die Anwednung liegt nur auf einem Server...?

Danke & Gruß,
Buzzy

Glombi:
Die bösesten Bugs bzgl. Soft-Locking wurden in 6.0.4/6.5.2 behoben. Damit sollte es gehen.

Andreas

Navigation

[0] Themen-Index

[#] Nächste Seite