Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
7.1.X, 7.2.X, Master
-
7.2.x, 7.1.x
-
Committed
-
3
-
Search | S03 Sprint 2
Description
Missing debug trace in RemoteElasticsearchConnection.createTransportClient().
This is necessary in order to diagnose configuration problems, for example, see: LPS-97878
Steps to reproduce
- Install a new Liferay instance
- Install a Elasticsearch server (see: https://portal.liferay.dev/docs/7-2/deploy/-/knowledge_base/d/installing-elasticsearch )
- Configure Liferay with REMOTE Elasticsearch configuration (see: https://portal.liferay.dev/docs/7-2/deploy/-/knowledge_base/d/configuring-the-liferay-elasticsearch-connector )
- Execute a full reindex and verify search is working
- Stop Liferay
- Create a folder "log4j" inside of LIFERAY_HOME/osgi/
- Copy attached files log4j.dtd
and com.liferay.portal.search.elasticsearch6.impl-log4j-ext.xml
into LIFERAY_HOME/osgi/log4j folder
- Start Liferay and check log files
- Expected behavior: a debug trace with elasticsearch remote configuration is written to log
2019-07-04 11:29:57.519 DEBUG [Elasticsearch initialization thread][RemoteElasticsearchConnection:156] settings: {"client.transport.ignore_cluster_name":"false","client.transport.sniff":"true","cluster.name":"liferay-elasticsearch-pre","http.host":"_local_","monitor.jvm.gc.enabled":"false", ...
- Wrong behavior: no debug trace is written to log file
- Expected behavior: a debug trace with elasticsearch remote configuration is written to log
Attachments
Issue Links
- Discovered while testing
-
LPS-97878 NPE is produced in case sslKeystorePassword or sslTruststorePassword are not configured in XPack security
- Closed