Troubleshooting Free text search issues

Use the following topics to resolve Free text search issues in the Persona-based UI.

Indexing job fails

Symptoms
Indexing job fails.
Causes
The index-starter.jar file is missing in the class path section of the $TOP/bin/conf/env_settings.ini file.
Solution
  • Run the configureEnv.sh file.
  • Ensure that the full path of the index-starter.jar file is available in the class path section of the env_settings.ini file
  • Start the IBM® Product Master services.

Indexing job fails

Symptoms
Indexing job fails.
Causes
Either indexer, pim-collector, OpenSearch, or Hazelcast service is not running.
Solution
  • Check the status of all the services by using the following URLs.
    • indexer - http://<hostname>:<indexer-port>/actuator/health
      Example
      http://localhost:8090/actuator/health
    • pimcollector - http://<hostname>:<pimcollector-port>/actuator/health
      Example
      http://localhost:8091/actuator/health
    • hazelcast - http://<hostname>:<hazelcast-port>/actuator/health
      Example
      http://localhost:5702/actuator/health
    • OpenSearch - http://<hostname>:<opensearch-port>
      Example
      http://localhost:9200
  • Start the service that is not running.

An item is not getting indexed

Symptoms
An item is not getting indexed.
Causes
Either indexer, pimcollector, OpenSearch, or Hazelcast service is not running.
Solution
  • Check the status of all the services by using the following URLs.
  • indexer - http://<hostname>:<indexer-port>/actuator/health
    Example
    http://localhost:8090/actuator/health
  • pimcollector - http://<hostname>:<pimcollector-port>/actuator/health
    Example
    http://localhost:8091/actuator/health
  • hazelcast - http://<hostname>:<hazelcast-port>/actuator/health
    Example
    http://localhost:5702/actuator/health
  • OpenSearch - http://<hostname>:<opensearch-port>
    Example
    http://localhost:9200
  • Start the service that is not running.

OutOfMemory error in the log files of the OpenSearch service

Symptoms
You see a OutOfMemory error in the OpenSearch service log files.
Causes
Memory is insufficient.
Solution
Restrict memory usage of OpenSearch service by adding -Xmx and -Xms options (small memory) in the OpenSearch-install-dir/config/jvm.options file.

Indexer service is not starting

Symptoms
Indexer service is not starting.
Causes
Incorrect value for the java17_home in the env_settings.ini file.
Solution
  • Set the value of the java17_home as ibm semeru jre11 the env_settings.ini file.
  • Restart the IBM Product Master services.
  • Verify that the start_indexer.sh file has updated the JRE path for the java17_home.

Free text search result is not showing some items

Symptoms
Free text search result is not showing some items.
Causes
Items might not be indexed.
Solution
  • Schedule a full indexing job.
  • Search such items after the job completes successfully.

Free text search result shows new or deleted attributes

Symptoms
Free text search result shows new or deleted attributes.
Causes
Items might be indexed with old attributes.
Solution
  • Schedule a full indexing job.
  • Search such items after the job completes successfully.

Certificate_unknown message appears in the log file

Symptoms
Certificate_unknown message appears in the log file.
Causes
Missing certificate entry in the cacerts file.
Solution
Import the OpenSearch certificate in the cacerts file of your installed jdk8 and jdk11.

javax.net.ssl.SSLHandshakeException error

Symptoms
You get the javax.net.ssl.SSLHandshakeException: Client requested protocol TLSv1 is not enabled or supported in server context error message and you have enabled SSL for OpenSearch.
Causes
The Java™ virtual machine (JVM) argument is a missing overrideDefaultTLS property in the start_indexer.sh file and JVM settings of the WebSphere® Application Server.
Solution
Set the overrideDefaultTLS property in the start_indexer.sh file and JVM settings of the WebSphere Application Server. For more information, see the Step 5 in the Configure WebSphere Application Server for OpenSearch.

OutOfMemory error in the log files of the Hazelcast service

Symptoms
You see a OutOfMemory error in the Hazelcast service log files.
Causes
Memory is insufficient.
Solution
Restrict memory usage of Hazelcast service by adding -Xmx and -Xms options (small memory) in the hazelcast-install-dir/config/jvm.options file.