legacy-knowledge-base
公開されました Jun. 30, 2025

コンソールで継続的に例外が発生するため、Liferay サービスが開始されない

written-by

Kanchan Bisht

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

learn-legacy-article-disclaimer-text

問題

  • DXP が起動に失敗し、ターミナルに次のエラーと警告が表示されます
    • ERROR [Portal Dependency Manager Component Executor--2][ElasticsearchSearchEngine:56] bundle com.liferay.portal.search.elasticsearch7.impl:6.0.61 (1555)[com.liferay.portal.search.elasticsearch7.internal.ElasticsearchSearchEngine(5416)] : The activate method has thrown an exception
      com.liferay.portal.search.elasticsearch7.internal.connection.ElasticsearchConnectionNotInitializedException: Elasticsearch connection not found. Production Mode Enabled: false, Connection ID: null, Prefer Local Cluster: true, Cross-Cluster Replication Enabled: false. Enable INFO logs on class com.liferay.portal.search.elasticsearch7.internal.connection.ElasticsearchConnectionManager for more information
      at com.liferay.portal.search.elasticsearch7.internal.connection.ElasticsearchConnectionManager.getRestHighLevelClient(ElasticsearchConnectionManager.java:193) ~[?:?]
      at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.cluster.HealthClusterRequestExecutorImpl._getClusterHealthResponse(HealthClusterRequestExecutorImpl.java:91) ~[?:?]
      at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.cluster.HealthClusterRequestExecutorImpl.execute(HealthClusterRequestExecutorImpl.java:49) ~[?:?]
      at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.cluster.ElasticsearchClusterRequestExecutor.executeClusterRequest(ElasticsearchClusterRequestExecutor.java:53) ~[?:?]
      at com.liferay.portal.search.engine.adapter.cluster.HealthClusterRequest.accept(HealthClusterRequest.java:40) ~[?:?]
      at com.liferay.portal.search.engine.adapter.cluster.HealthClusterRequest.accept(HealthClusterRequest.java:22) ~[?:?] .................................................................................................................................................................................WARN [Portal Dependency Manager Component Executor--2][IndexSearcherHelperImpl:62] bundle com.liferay.portal.search:8.0.47 (1122)[com.liferay.portal.search.internal.IndexSearcherHelperImpl(4020)] : Could not get service from ref {com.liferay.portal.kernel.search.SearchEngineHelper}={component.id=4028, component.name=com.liferay.portal.search.internal.SearchEngineHelperImpl, service.id=5286, service.scope=bundle, service.bundleid=1122}
      ...........................................................................................
      WARN [Framework Event Dispatcher: Equinox Container: 743e87ac-5dd1-4cdc-814c-c518784bb7cd][Framework:62] FrameworkEvent WARNING
      org.osgi.framework.ServiceException: org.apache.felix.scr.impl.manager.SingleComponentManager.getService() returned a null service object
      at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:232) ~[org.eclipse.osgi.jar:?]
      at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.getService(ServiceFactoryUse.java:111) ~[org.eclipse.osgi.jar:?]

Environment

  • Liferay DXP 7.4
  • 組み込みのエラスティックサーチ

解決策

  • このシナリオでは、 Liferay_home 内の elasticsearch-sidecar フォルダーを確認して、フォルダーまたはファイルのいずれかが見つからないか破損しているかどうかを確認してください。
    • 上記のシナリオが該当する場合、最も簡単な回避策は、このフォルダー全体を同じバニラ アップデートの新しいフォルダーに置き換えて、サーバーを再起動することです。
    • サーバーを再起動する前に、すべての一時フォルダーをクリアします。
      1. Delete liferay_home/osgi/state
      2. Delete liferay_home/work
      3. Delete liferay_home/tomcat/work
      4. Delete liferay_home/tomcat/temp
      5. Restart the server

追加情報

  • 推奨されるアプローチは、常に、最初に下位環境で上記のアクティビティまたは操作を実行し、完全なシャットダウン状態で実行することです。
did-this-article-resolve-your-issue

legacy-knowledge-base