Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

RankingIndexCreationBundleActivator error after running an upgrade

Written By

Debora Vita

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • After running an upgrade, we found the following errors in the logs:

    2023-11-29 22:13:14.432 ERROR [SystemExecutorServiceUtil-4-com.liferay.portal.spring.extender.internal.configuration.ServiceConfigurationInitializer-com.liferay.portal.lock.service][ROOT:47] bundle com.liferay.portal.search.tuning.rankings.web:3.0.67 (1283)[com.liferay.portal.search.tuning.rankings.web.internal.index.creation.activator.RankingIndexCreationBundleActivator(10040)] : The activate method has thrown an exception

    java.lang.RuntimeException: org.elasticsearch.ElasticsearchStatusException: ElasticsearchStatusException[method [HEAD], host [https://esaas-src-p.bankofamerica.com], URI [/liferay-search-tuning-rankings?include_type_name=true], status line [HTTP/1.1 403 Forbidden]]; nested: ResponseException[method [HEAD], host [https://esaas-src-p.bankofamerica.com], URI [/liferay-search-tuning-rankings?include_type_name=true], status line [HTTP/1.1 403 Forbidden]];

        at org.elasticsearch.client.RestHighLevelClient.parseResponseException(RestHighLevelClient.java:2458) ~[?:?]

        at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:2184) ~[?:?]

        at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:2137) ~[?:?]

        at org.elasticsearch.client.IndicesClient.exists(IndicesClient.java:1321) ~[?:?]

        at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.index.IndicesExistsIndexRequestExecutorImpl._indicesExists(IndicesExistsIndexRequestExecutorImpl.java:61) ~[?:?]

        at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.index.IndicesExistsIndexRequestExecutorImpl.execute(IndicesExistsIndexRequestExecutorImpl.java:34) ~[?:?]

Environment

  • DXP 7.4

Resolution

  • At startup, the SingleIndexToMultipleIndexImporterImpl class tries to import the Result Rankings from the old liferay-search-tuning-rankings index to the new liferay-<companyId>-search-tuning-rankings index. This happens at each and every startup because the portal doesn't know if the environment is a fresh environment or a migrated one from a previous version where the index's name was liferay-search-tuning-rankings.
  • If the environment is a fresh installation, the liferay-search-tuning-rankings index doesn't exist at all, but the import still tries to execute.
  • Our recommendation would be to ignore the error as it should have no effect on your installation, or you can resolving it by granting access to the user for the old index name.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?