Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 5 Advanced Topics : Repository Locking

Repository Locking
When an administration server accesses a repository for update, the repository is marked as locked so that other servers cannot update the same repository.
Once a repository is locked, it remains so until the server is cleanly shut down. For local file repositories, the lock is released when the client is destroyed.
The file exists in the same directory as the project file, but has a .lck extension.
Database. In the case of a database backend, the Instance table has the locker column set to the server name for that particular instance.
How to Break the Lock
In some situations, a repository may remain locked although it is actually no longer in use.
For server-based repository, you can break the lock by setting the repo.forceInstanceLocks property in the tibcoadmin_domain-name.tra file to true and restarting the administration server. See also Administration Server Properties File for additional details.
For local file repositories, a lock file exists in the same directory as the project file and has a .lck extension rather than a .dat extension. You can force the removal of a lock on a repository by deleting its .lck file.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved