Unable to prepare a release document in Simonsoft CMS with error message "Exception in thread "main"

Description

• ​​Trying to prepare a release/translation but get error about "Exception in thread "main" org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: this writer hit an OutOfMemoryError; cannot commit"
  

• Unable to see "Used In" on an object in Simonsoft CMS

• Clicking on Prepare Relase gives following error message:
  
  

  Exception in thread "main" org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: this writer hit an OutOfMemoryError; cannot commit
          at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:495)
          at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:199)
          at org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:118)
          at org.apache.solr.client.solrj.SolrServer.commit(SolrServer.java:168)
          at org.apache.solr.client.solrj.SolrServer.commit(SolrServer.java:146)
          at se.repos.indexing.solrj.SolrCommit.runOp(SolrCommit.java:24)
          at se.repos.indexing.solrj.SolrOp.run(SolrOp.java:29)
          at se.repos.indexing.solrj.MarkerCommitSolrj.trigger(MarkerCommitSolrj.java:33)
          at se.repos.indexing.scheduling.HandlerIteration.proceed(HandlerIteration.java:80)
          at se.repos.indexing.scheduling.IndexingScheduleBlockingOnly.run(IndexingScheduleBlockingOnly.java:82)
          at se.repos.indexing.scheduling.IndexingScheduleBlockingOnly.add(IndexingScheduleBlockingOnly.java:56)
          at se.repos.indexing.repository.ReposIndexingPerRepository.sync(ReposIndexingPerRepository.java:222)
          at se.repos.indexing.standalone.IndexingDaemon.runOnce(IndexingDaemon.java:287)
          at se.repos.indexing.standalone.IndexingDaemon.run(IndexingDaemon.java:221)
          at se.repos.indexing.standalone.CommandLine.runDaemon(CommandLine.java:170)
          at se.repos.indexing.standalone.CommandLine.main(CommandLine.java:109)

Cause

• ​The CMS server out of memory

• Indexing service is down

Resolution

• Contact ​​PDSVISION Support

• Index service down

• A restart of Tomcat service is needed