Existing lock file .lock detected. Repository was not shut down properly

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.




    Footprints 12 and above


    When Tomcat service stopped by killing process directly, repository lock may  not released by tomcat process. When you restart the service, Footprints throws 404 error with following log entry

    WARN |2019-11-06T14:03:30.640|CST|FootPrints|localhost-startStop-1|org.apache.jackrabbit.core.util.RepositoryLock.acquire()|||Existing lock file C:\Program Files\BMC Software\FootPrints Service Core\repository\.lock detected. Repository was not shut down properly.|

    RL [jar:file:/C:/Program%20Files/BMC%20Software/FootPrints%20Service%20Core/web/WEB-INF/lib/core-53.3362.jar!/com/numarasoftware/footprints/core/filestorage/jackrabbit/JackRabbitSessionFactory.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jackRabbitRepositoryFactory': Invocation of init method failed; nested exception is com.numarasoftware.footprints.core.filestorage.FileStorageServiceException: Repository configuration error.



    • Stop the tomcat service . Clear the logs and temp files
    • Verify Tomcat service account has full control permission
    • Verify that  :\Program Files\Apache Software Foundation\Tomcat XX\conf\Catalina\localhost folder does not contain more that one  footprints#servicdesk.xml file


    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles