Locks are valid for the time of a session in your Tomcat (default : 30 min)
in X:\jahia\tomcat\conf\web.xml
<!-- ==================== Default Session Configuration ================= -->
<!-- You can set the default session timeout (in minutes) for all newly -->
<!-- created sessions by modifying the value below. -->
<session-config>
<session-timeout>30</session-timeout>
</session-config>Locks should prevent two users to edit simultaneously the same content (excepted if a user closed a pop-up with the Windows close icon and not the Jahia Cancel button. In such a case, Jahia has no way to know that the user left the window as the browser does not send any information back to the server. So try to train your users to use the cancel button). So this is not suggested to reduce the session time. Indeed if an author spend more than his session time in an engine, he will loose his login and then his content and will have to relog... and lots of users usually spend more than 30 minutes in the HTML editors!
If a content manager really knows that the other user left the engine, he may steal his lock at any time. This should be a better solution than reducing the session time (usually you tend to increase it).
You can also flush all the locks in the Root menu in the Admin Center (in the Cache menu).
Cheers St�phane
At 17:00 27/08/2004, you wrote:
Hi,
I would like to know if it is possible to configure lock time?
The resource is already locked for modification. Close any engine that might be using this resource and try again.
Object locked by user : user1
Lock name : Add_ContentContainerList_22
Remaining time : 0 h 29 m 13 s
Thx in advance
Acc�dez au courrier �lectronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34�/mn) ; t�l : 08 92 68 13 50 (0,34�/mn)
