https://community.appian.com/support/w/kb/624/kb-1262-lock-obtain-timed-out-error-thrown-when-starting-the-application-serveren-USTelligent Community 12https://community.appian.com/support/w/kb/624/kb-1262-lock-obtain-timed-out-error-thrown-when-starting-the-application-serverMon, 23 Jul 2018 03:42:04 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:ae25f61d-f2b5-4c66-a66c-f1343178f5c3Parmida Borhanihttps://community.appian.com/support/w/kb/624/kb-1262-lock-obtain-timed-out-error-thrown-when-starting-the-application-server#commentsCurrent Revision posted to Appian Knowledge Base by Parmida Borhani on 7/23/2018 3:42:04 AM<br /> <h2>Symptoms</h2> <p>The following error is seen in the application server log:</p> <pre>[Appian ReschedulingTimerTask - SearchIndexSyncTimerTask - XXXXX] ERROR com.appiancorp.rdbms.common.search.SearchIndexSyncTimerTask - [Search index sync: jdbc/XXXX] XXXX consecutive errors. Will try again in XXXX ms.<br /> ...<br /> Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out:&lt;APPIAN_HOME&gt;/_admin/search-local/index-primary/com.appiancorp.tempo.rdbms.EventFeedEntry/write.lock</pre> <h2>Cause</h2> <p>This error typically occurs when the application server is improperly shut down.</p> <p>In a distributed environment, this error can occur if the network drive where <code>&lt;APPIAN_HOME&gt;/_admin</code> resides becomes unavailable while the application server is starting up or shutting down. The network drive becoming unavailable would prevent the deletion of the <strong>write.lock</strong> file.</p> <h2>Action</h2> <ol> <li>Stop the application server.</li> <li>Delete the <strong>write.lock</strong> file in <code>&lt;APPIAN_HOME&gt;/_admin/search-local/index-primary/com.appiancorp.tempo.rdbms.EventFeedEntry</code>.</li> <li>Restart the application server.</li> </ol> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p>Last Reviewed: June 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: application server, infrastructure</div> https://community.appian.com/support/w/kb/624/kb-1262-lock-obtain-timed-out-error-thrown-when-starting-the-application-server/revision/2Thu, 16 Nov 2017 08:33:03 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:ae25f61d-f2b5-4c66-a66c-f1343178f5c3Nick Vigilantehttps://community.appian.com/support/w/kb/624/kb-1262-lock-obtain-timed-out-error-thrown-when-starting-the-application-server#commentsRevision 2 posted to Appian Knowledge Base by Nick Vigilante on 11/16/2017 8:33:03 AM<br /> <h2>Symptoms</h2> <p>The following error is seen in the application server log:</p> <pre>[Appian ReschedulingTimerTask - SearchIndexSyncTimerTask - XXXXX] ERROR com.appiancorp.rdbms.common.search.SearchIndexSyncTimerTask - [Search index sync: jdbc/XXXX] XXXX consecutive errors. Will try again in XXXX ms.<br /> ...<br /> Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out:&lt;APPIAN_HOME&gt;/_admin/search-local/index-primary/com.appiancorp.tempo.rdbms.EventFeedEntry/write.lock</pre> <h2>Cause</h2> <p>This error typically occurs when the application server is improperly shut down.</p> <p>In a distributed environment, this error can occur if the network drive where <code>&lt;APPIAN_HOME&gt;/_admin</code> resides becomes unavailable while the application server is starting up or shutting down. The network drive becoming unavailable would prevent the deletion of the <strong>write.lock</strong> file.</p> <h2>Action</h2> <ol> <li>Stop the application server.</li> <li>Delete the <strong>write.lock</strong> file in <code>&lt;APPIAN_HOME&gt;/_admin/search-local/index-primary/com.appiancorp.tempo.rdbms.EventFeedEntry</code>.</li> <li>Restart the application server.</li> </ol> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p>Last Reviewed: June 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: application server</div> https://community.appian.com/support/w/kb/624/kb-1262-lock-obtain-timed-out-error-thrown-when-starting-the-application-server/revision/1Mon, 12 Jun 2017 17:39:01 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:ae25f61d-f2b5-4c66-a66c-f1343178f5c3Nick Vigilantehttps://community.appian.com/support/w/kb/624/kb-1262-lock-obtain-timed-out-error-thrown-when-starting-the-application-server#commentsRevision 1 posted to Appian Knowledge Base by Nick Vigilante on 6/12/2017 5:39:01 PM<br /> <h2>Symptoms</h2> <p>The following error is seen in the application server log:</p> <pre>[Appian ReschedulingTimerTask - SearchIndexSyncTimerTask - XXXXX] ERROR com.appiancorp.rdbms.common.search.SearchIndexSyncTimerTask - [Search index sync: jdbc/XXXX] XXXX consecutive errors. Will try again in XXXX ms.<br /> ...<br /> Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out:&lt;APPIAN_HOME&gt;/_admin/search-local/index-primary/com.appiancorp.tempo.rdbms.EventFeedEntry/write.lock</pre> <h2>Cause</h2> <p>This error typically occurs when the application server is improperly shut down.</p> <p>In a distributed environment, this error can occur if the network drive where <code>&lt;APPIAN_HOME&gt;/_admin</code> resides becomes unavailable while the application server is starting up or shutting down. The network drive becoming unavailable would prevent the deletion of the <strong>write.lock</strong> file.</p> <h2>Action</h2> <p>1. Stop the application server.<br />1. Delete the <strong>write.lock</strong> file in <code>&lt;APPIAN_HOME&gt;/_admin/search-local/index-primary/com.appiancorp.tempo.rdbms.EventFeedEntry</code>.<br />1. Restart the application server.</p> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p>Last Reviewed: June 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: application server</div>