フィードバックを送信
legacy-knowledge-base
公開されました Sep. 10, 2025

JBoss EAP サーバーの起動時に NullPointerException/ElasticsearchConnectionNotInitializedException/ArrayIndexOutOfBoundsException が発生する。

written-by

Emma Liu

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

問題

  • JBoss EAPサーバーにLiferay DXP 7.3/7.4をデプロイしたところ、以下のエラーによりサーバーを起動できない：
10:17:20,354 INFO 2022-02-17 10:17:20.308 ERROR [Framework Event Dispatcher: Equinox Container: b091645f-c27f-4506-9dd2-ba5088937c54][Framework:93] FrameworkEvent ERROR 
10:17:20,355 INFO java.lang.NullPointerException: null
10:17:20,356 INFO at com.liferay.portal.search.internal.SearchEngineHelperImpl$1.addingService(SearchEngineHelperImpl.java:318) ~[?:?]
10:17:20,356 INFO at com.liferay.portal.search.internal.SearchEngineHelperImpl$1.addingService(SearchEngineHelperImpl.java:308) ~[?:?]
10:17:20,356 INFO at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:943) ~[org.eclipse.osgi.jar:?]
10:17:20,357 INFO at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:1) ~[org.eclipse.osgi.jar:?]
10:17:20,357 INFO at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256) ~[org.eclipse.osgi.jar:?]
10:17:20,357 INFO at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229) ~[org.eclipse.osgi.jar:?]
10:17:20,357 INFO at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:903) ~[org.eclipse.osgi.jar:?]
10:17:20,357 INFO at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109) ~[org.eclipse.osgi.jar:?]
10:17:20,358 INFO at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:891) ~[org.eclipse.osgi.jar:?]
10:17:20,358 INFO at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:804) ~[org.eclipse.osgi.jar:?]
10:17:20,358 INFO at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127) ~[org.eclipse.osgi.jar:?]
10:17:20,358 INFO at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:228) ~[org.eclipse.osgi.jar:?]
.......
10:17:31,262 INFO [io.undertow.servlet] (Context initialized thread for speedwell-theme) Initializing Spring root WebApplicationContext
10:17:35,475 INFO [io.undertow.servlet] (Context initialized thread for minium-theme) Initializing Spring root WebApplicationContext
10:17:35,725 INFO 2022-02-17 10:17:35.681 ERROR [Portal Dependency Manager Component Executor--1][RankingIndexCreationBundleActivator:93] bundle com.liferay.portal.search.tuning.rankings.web:3.0.14 (1424)[com.liferay.portal.search.tuning.rankings.web.internal.index.creation.activator.RankingIndexCreationBundleActivator(9425)] : The activate method has thrown an exception 
10:17:35,726 INFO 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
10:17:35,726 INFO at com.liferay.portal.search.elasticsearch7.internal.connection.ElasticsearchConnectionManager.getRestHighLevelClient(ElasticsearchConnectionManager.java:192) ~[?:?]
10:17:35,726 INFO at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.index.IndicesExistsIndexRequestExecutorImpl.indicesExists(IndicesExistsIndexRequestExecutorImpl.java:63) ~[?:?]
10:17:35,726 INFO at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.index.IndicesExistsIndexRequestExecutorImpl.execute(IndicesExistsIndexRequestExecutorImpl.java:43) ~[?:?]
10:17:35,726 INFO at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.index.ElasticsearchIndexRequestExecutor.executeIndexRequest(ElasticsearchIndexRequestExecutor.java:118) ~[?:?]
10:17:35,726 INFO at com.liferay.portal.search.engine.adapter.index.IndicesExistsIndexRequest.accept(IndicesExistsIndexRequest.java:36) ~[?:?]
10:17:35,726 INFO at com.liferay.portal.search.engine.adapter.index.IndicesExistsIndexRequest.accept(IndicesExistsIndexRequest.java:22) ~[?:?]
10:17:35,727 INFO at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.ElasticsearchSearchEngineAdapterImpl.execute(ElasticsearchSearchEngineAdapterImpl.java:91) ~[?:?]
10:17:35,727 INFO at com.liferay.portal.search.tuning.rankings.web.internal.index.RankingIndexReaderImpl.isExists(RankingIndexReaderImpl.java:82) ~[?:?]
10:17:35,727 INFO at com.liferay.portal.search.tuning.rankings.web.internal.index.importer.SingleIndexToMultipleIndexImporterImpl.needImport(SingleIndexToMultipleIndexImporterImpl.java:83) ~[?:?]
10:17:35,727 INFO at com.liferay.portal.search.tuning.rankings.web.internal.index.creation.activator.RankingIndexCreationBundleActivator.activate(RankingIndexCreationBundleActivator.java:45) ~[?:?]
10:17:35,727 INFO at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_311]
10:17:35,727 INFO at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_311]
.......
10:17:39,055 INFO [io.undertow.servlet] (Context initialized thread for admin-theme) Initializing Spring root WebApplicationContext
10:17:42,361 INFO [io.undertow.servlet] (Context initialized thread for classic-theme) Initializing Spring root WebApplicationContext
10:18:08,989 INFO (liferay/scheduler_dispatch-6) 2022-02-17 10:18:08.963 ERROR [liferay/scheduler_dispatch-6][ParallelDestination:59] Unable to process message {destinationName=liferay/scheduler_dispatch, response=null, responseDestinationName=null, responseId=null, payload=null, values={GROUP_NAME=com.liferay.server.admin.web.internal.messaging.PluginRepositoriesMessageListener, companyId=0, groupId=0, DESTINATION_NAME=liferay/scheduler_dispatch, EXCEPTIONS_MAX_SIZE=0, JOB_STATE=com.liferay.portal.kernel.scheduler.JobState@22336ba8, STORAGE_TYPE=MEMORY_CLUSTERED, JOB_NAME=com.liferay.server.admin.web.internal.messaging.PluginRepositoriesMessageListener}}
10:18:08,990 INFO (liferay/scheduler_dispatch-6) com.liferay.portal.kernel.messaging.MessageListenerException: 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
10:18:08,990 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.kernel.messaging.BaseMessageListener.receive(BaseMessageListener.java:41) ~[portal-kernel.jar:?]
10:18:08,990 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.kernel.scheduler.messaging.SchedulerEventMessageListenerWrapper._processMessage(SchedulerEventMessageListenerWrapper.java:127) ~[portal-kernel.jar:?]
10:18:08,990 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.kernel.scheduler.messaging.SchedulerEventMessageListenerWrapper.receive(SchedulerEventMessageListenerWrapper.java:98) ~[portal-kernel.jar:?]
10:18:08,990 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.kernel.messaging.InvokerMessageListener.receive(InvokerMessageListener.java:74) ~[portal-kernel.jar:?]
10:18:08,990 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.messaging.internal.ParallelDestination$1.run(ParallelDestination.java:56) [bundleFile:?]
10:18:08,990 INFO (liferay/scheduler_dispatch-6) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_311]
10:18:08,990 INFO (liferay/scheduler_dispatch-6) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_311]
10:18:08,990 INFO (liferay/scheduler_dispatch-6) at java.lang.Thread.run(Thread.java:748) [?:1.8.0_311]
10:18:08,990 INFO (liferay/scheduler_dispatch-6) Caused by: 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
10:18:08,990 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.search.elasticsearch7.internal.connection.ElasticsearchConnectionManager.getRestHighLevelClient(ElasticsearchConnectionManager.java:192) ~[?:?]
10:18:08,990 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.cluster.HealthClusterRequestExecutorImpl.getClusterHealthResponse(HealthClusterRequestExecutorImpl.java:91) ~[?:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.cluster.HealthClusterRequestExecutorImpl.execute(HealthClusterRequestExecutorImpl.java:49) ~[?:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.cluster.ElasticsearchClusterRequestExecutor.executeClusterRequest(ElasticsearchClusterRequestExecutor.java:53) ~[?:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.search.engine.adapter.cluster.HealthClusterRequest.accept(HealthClusterRequest.java:40) ~[?:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.search.engine.adapter.cluster.HealthClusterRequest.accept(HealthClusterRequest.java:22) ~[?:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.cluster.ElasticsearchClusterRequestExecutor.execute(ElasticsearchClusterRequestExecutor.java:46) ~[?:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.ElasticsearchSearchEngineAdapterImpl.execute(ElasticsearchSearchEngineAdapterImpl.java:69) ~[?:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.search.elasticsearch7.internal.ElasticsearchSearchEngine.waitForYellowStatus(ElasticsearchSearchEngine.java:383) ~[?:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.search.elasticsearch7.internal.ElasticsearchSearchEngine.initialize(ElasticsearchSearchEngine.java:144) ~[?:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.kernel.search.SearchEngineProxyWrapper.initialize(SearchEngineProxyWrapper.java:66) ~[portal-kernel.jar:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.search.internal.SearchEngineHelperImpl.initialize(SearchEngineHelperImpl.java:222) ~[?:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.kernel.search.SearchEngineHelperUtil.initialize(SearchEngineHelperUtil.java:87) ~[portal-kernel.jar:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.server.admin.web.internal.messaging.PluginRepositoriesMessageListener.doReceive(PluginRepositoriesMessageListener.java:86) ~[?:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) at com.liferay.portal.kernel.messaging.BaseMessageListener.receive(BaseMessageListener.java:31) ~[portal-kernel.jar:?]
10:18:08,991 INFO (liferay/scheduler_dispatch-6) ... 7 more
10:18:14,136 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 81) WFLYUT0021: Registered web context: '/ROOT' for server 'default-server'
10:18:14,408 INFO [org.jboss.as.server] (ServerService Thread Pool -- 45) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
10:18:14,649 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
10:18:14,668 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.4.0.GA (WildFly Core 15.0.2.Final-redhat-00001) started in 189971ms - Started 534 of 774 services (468 services are lazy, passive or on-demand)
10:18:14,672 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
10:18:14,673 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
10:20:57,160 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ROOT/home: java.lang.ArrayIndexOutOfBoundsException: 0
at com.liferay.portal.util.PortalInstances.getDefaultCompanyId(PortalInstances.java:203)
at com.liferay.portal.util.PortalImpl.getDefaultCompanyId(PortalImpl.java:2161)
at com.liferay.portal.kernel.util.PortalUtil.getDefaultCompanyId(PortalUtil.java:863)
at com.liferay.portal.servlet.filters.validhostname.ValidHostNameFilter.doFilterTry(ValidHostNameFilter.java:39)
at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.processDirectCallFilter(InvokerFilterChain.java:194)
at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:99)
at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilter.doFilter(InvokerFilter.java:104)
at com.liferay.shielded.container.internal.proxy.FilterWrapper.doFilter(FilterWrapper.java:79)
at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
.......

Environment

  • Liferay DXP 7.3
  • Liferay DXP 7.4

解決策

  • エラーの原因は、Elasticsearchが正常に初期化されていないことです。 二重確認のため、 liferay_home/elasticsearch7 (DXP 7.3) または liferay_home/elasticsearch-sidecar (DXP 7.4) フォルダ内にコンテンツがあるかどうかを確認してください。 フォルダが空の場合は、以下のオプションで解決してください。

  • オプション1：

    • 起動時にsidecarが自動ダウンロードされるため、外部のネットワークにアクセスできることを確認してください。 こちらについて言及しています。

  • オプション2：
    • elasticsearch7 (DXP 7.3)/elasticsearch-sidecar (DXP 7.4) フォルダーを別の作業環境から現在の環境に手動でコピーします。
      1. elasticsearch7 (DXP 7.3)/elasticsearch-sidecar (DXP 7.4) フォルダを liferay_home から削除します（存在する場合）。
      2. elasticsearch7 (DXP 7.3)/elasticsearch-sidecar (DXP 7.4) フォルダを作業環境から現環境の Liferay_homeにコピーします。
      3. サーバーを再起動する。

did-this-article-resolve-your-issue
legacy-knowledge-base
did-this-article-resolve-your-issue