-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IndexOutOfBoundsException in sitesearch portlet #28779
Comments
Another Customer hitting this: https://dotcms.zendesk.com/agent/tickets/116552 Workaround It was to remove the default SS index directly from the DB and flush the cache. Afterwards, the portlet started to show up, and we were able to set up the SS index default again. |
I've observed this issue with customers a few times; the most common cause is the non-existence of the Default index. Let's implement validation for this and also add a WARN log when the Default index isn't present. |
Fixed, this is working as expected, no error after delete the index Tested on [ trunk_78bb755 ] // Docker |
This does not apply to 23.01 LTS since the code doesn't exist. |
Parent Issue
No response
Problem Statement
A customer reported an issue related to sitesearch and in the logs shows.
Steps to Reproduce
This line throws an error
core/dotCMS/src/enterprise/java/com/dotcms/enterprise/publishing/sitesearch/ESSiteSearchAPI.java
Line 163 in 8b71ba0
Because list.indexOf(defaultIndice); returns -1 if default indices are not there in the list
The root cause is here.
indiciesAPI.loadIndicies() returns different results
core/dotCMS/src/enterprise/java/com/dotcms/enterprise/publishing/sitesearch/ESSiteSearchAPI.java
Line 161 in 8b71ba0
Acceptance Criteria
The logic error should handle and indexoutofbound should never return if difference in indeces
dotCMS Version
24.*
Proposed Objective
Customer Support
Proposed Priority
Priority 4 - Trivial
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
https://dotcms.zendesk.com/agent/tickets/116403
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: