Skip to main content
Hitachi Vantara Lumada and Pentaho Documentation

Jackrabbit Repository Performance Tips

Clean Out Old Jackrabbit Repository Data

Jackrabbit Repository (JCR) will often hang on to a lot of unused data if you perform migrations from the same repository multiple times. This leads to an increase in table sizes and slowdowns on the repository. You can clean up this unused data in the JCR by enabling a system listener designed for this purpose.

Cleaning up the JCR can only be done with no users logged into it and locks the repository for as long as the process is running. 

  1. Stop the BA Server.
  2. Locate the ...biserver-ee/pentaho-solutions/system  directory and open the systemListeners.xml with any text editor.
  3. Add this bean as the last item within the list tags.
<bean id="repositoryCleanerSystemListener" class="">
<property name="gcEnabled" value="true"/>
<property name="execute" value="now"/>
  1. Save and close the systemListeners.xml file and restart the BA Server.

You can customize the settings for the repositoryCleanerSystemListener by editing these properties.

Property Description
gcEnabled This is a Boolean flag that turns the listener On (true) or Off (false).
execute You can chose to run the listener:
  • now - runs once during server start-up
  • weekly - runs on the first day of each week (Sunday)
  • monthly - runs on the first day of each month