Relevance Module Troubleshooting

Overview

This page lists common issues with the Relevance Module and provides steps to resolve them.

Relevance Module does not function after adding to project
Visitor data is not collected
Realtime tab in Content Audiences shows "Could not read. The server returned status code 500 (Internal Server Error)."
Relevance REST service returns 500 Internal Server Error
Trends tab displays no data
Persona property "comes from" shows only two locations (Amsterdam, NL and Cambridge, US)
CMS startup error: "can't merge a nested mapping"

Common Issues and Resolutions

Relevance Module does not function after adding to project

Symptom

The Relevance Module is present in the project but does not work as expected.

Resolution

Confirm that all required Maven dependencies are included in the project.
Ensure that data stores are configured correctly.

Visitor data is not collected

Symptom

No visitor data appears in the system.

Resolution

Verify that collectors are configured correctly.
To add more collectors, include the Collectors Bundle in your project.
Use the Relevance REST services to confirm that visitor data is being collected.

Realtime tab in Content Audiences shows "Could not read. The server returned status code 500 (Internal Server Error)."

Symptom

The Realtime tab in the Content Audiences application displays a 500 Internal Server Error.

Cause

The CMS receives a 500 response from the Relevance REST service, often due to incorrect data store configuration.

Resolution

Review application logs for error messages or stack traces.
Confirm that data stores are configured correctly.
Ensure that both the SQL database and Elasticsearch are running and accessible.

Relevance REST service returns 500 Internal Server Error

Symptom

The Relevance REST service responds with a 500 Internal Server Error.

Cause

This usually indicates a problem with data store configuration.

Resolution

Check application logs for error messages or stack traces.
Verify that data stores are configured correctly.
Make sure the SQL database and Elasticsearch are operational and reachable.

Trends tab displays no data

Symptom

The Trends tab does not show any data.

Cause

This may be caused by an incorrectly configured visits data store or an unavailable Elasticsearch instance. If you see an error such as java.net.ConnectException: Connection refused, Elasticsearch is likely not running or unreachable.

Resolution

Review application logs for error messages.
Confirm that data stores are configured correctly, especially the visits store (Elasticsearch).
Ensure Elasticsearch is running.

Persona property "comes from" shows only two locations (Amsterdam, NL and Cambridge, US)

Symptom

The persona property "comes from" only lists Amsterdam, NL and Cambridge, US.

Cause

The available locations are defined in the GeoIPCollectorPlugin properties.

Resolution

Open the Console.
Navigate to /hippo:configuration/hippo:frontend/cms/hippo-targeting/collector-geo.
Add a new entry to the multi-valued string property locations using the format:
city | country code | latitude | longitude
Example:
```
Amsterdam | NL | 52.350006 | 4.9167023
```

CMS startup error: "can't merge a nested mapping"

Symptom

On CMS startup, the following error appears when initializing the Elasticsearch store from AbstractElasticStore.updateMapping:

{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"can't merge a nested mapping [requests] with a non-nested mapping"}],"type":"illegal_argument_exception","reason":"can't merge a nested mapping [requests] with a non-nested mapping"},"status":400}

Cause

Elasticsearch generated its own mapping for the "requests" object dynamically, instead of using the mapping initialized by the CMS. This can occur if the index is created while the CMS is already writing data to it.

Resolution

Recreate the Elasticsearch index.
Restart the CMS to allow it to initialize the mapping correctly.