How can we help?

My Cases

Corrupted Apache Lucene Indexes
Last Updated: Jun 08, 2015 11:15AM EDT

This article applies to:  Echo360 Admins


Sometimes a particular page or sub-page of the ESS user interface will not load and an error is instead displayed. Other pages load successfully, however.


This article is intended for use by ESS administrators when faced with errors similar to the below on their ESS user interface.


The error on the ESS interface will be similar to the following:

Error: ApplicationRuntimeException – Unable to read OGNL expression '<parsed OGNL expression>' of $RoomLink_80@7010998e[device/ShowDevice/deviceInfo.roomHistoryLink]: Invalid UUID string: 0 
  • Note: This is for a specific Room; that portion of the error may vary.


The ESS relies on Apache Lucene to provide search and display indexes for the various objects in the system (ie - Echoes, Captures, Rooms, etc.). These indexes are built from records in the database and maintained on the ESS filesystem. For various reasons these indexes can become corrupt, which then prevents the proper loading of one or more pages on the ESS.


In order to resolve this issue, the indexes of the ESS must be re-created. In order to do so, please follow these steps:

  1. Log into the ESS user interface.
  2. Navigate to the System > System Indexes tab of the ESS.
  3. Click 'Re-index All on Next ESS Restart'
  4. Restart the ESS service.
  5. Wait for several minutes to allow the index to be re-created.
  6. Log into the ESS interface again to confirm whether the issue has been resolved.
  • Note: If you are unable to reach the ESS interface due to an error similar to the above, then please stop the ESS service, delete the contents of the ${ESS_HOME}/echo360/server/db/index/ directory, the ${ESS_HOME}/echo360/server/.tmp directory, and the ${ESS_HOME}/echo360/server/work directory, and then restart the ESS service.
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found