<REPO_NAME> is already indexing, ignoring second indexing request

Symptoms

The following appears in the atlassian-stash.log:

"90.55 "POST /scm/<PROJECT>/<REPO_NAME>/git-receive-pack HTTP/1.1" c.a.s.i.i.i.Changes etIndexingServiceImpl Request for indexing of test-repo received
2012-10-10 16:10:01,868 DEBUG [pool-4-thread-1] <USER> 843x784x1 v7lj91 10.0.90.55 "POST /scm/<PROJECT>/<REPO_NAME>/git-receive-pack  HTTP/1.1" c.a.s.i.i.i.Changes etIndexingServiceImpl [<PROJECT>/<REPO_NAME>]  is already indexing, ignoring second indexing request" 

Diagnosis

The new commit does appear in Stash but there is no related to the JIRA issue that was mentioned in the Commit Comment. Also on JIRA the Source Tab on the issue does not display any information relating to the git commit.

Cause

Stash thinks it's already indexing that repository (when in fact it probably isn't). Because it thinks it's already in the process of indexing, it doesn't start indexing for the new pushes, so the commit information doesn't appear.

Resolution

1. Restart the Stash instance -  the list of what is being indexed, which it tests against to ensure it doesn't concurrently index - is maintained in memory, and will be cleared by the restart.

2. Then do exactly one push to the repository and the logs should show something like this in the Logs: 

   c.a.s.i.i.i.Changes etIndexingServiceImpl Request for indexing of test-repo received

3. The message that says it's already indexing should be gone and the integration should be working perfectly.