You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by "Juan Pablo Santos RodrÃguez (Jira)" <ji...@apache.org> on 2020/11/07 23:42:00 UTC
[jira] [Commented] (JSPWIKI-1131) Lucene Index not updated on
edits/new page
[ https://issues.apache.org/jira/browse/JSPWIKI-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17227877#comment-17227877 ]
Juan Pablo Santos RodrÃguez commented on JSPWIKI-1131:
------------------------------------------------------
Hi [~uo5waiBil9],
the code indexing a page save is the same that indexes all the pages at the startup, so I don't know where else to look to reproduce your issue; latest push includes functional tests for search actions. Other than maven and a jdk, these tests only require to have Chrome executable available on $PATH
The fastest way to verify their behaviour against a prepared JSPWiki war is to
{code:java}
mvn clean install -pl jspwiki-it-tests/jspwiki-it-test-custom -am -Pintegration-tests
{code}
You may also run the functional tests individually from your IDE, against your running instance. To do so, locate the class {{org.apache.wiki.its.environment.Env}} on the jspwiki-selenide-tests and modify the {{TESTS_BASE_URL}} variable, so it points to your running instance. After that, you may run the {{org.apache.wiki.its.SearchIT}} as a regular test from within your IDE. Would you mind verifying if these two approaches (functional tests against prepared war vs functional test against you running instance) yield different results?
Also, a couple more points that may help pinpoint your issue
* latest push updates the version of Lucene to latest, 8.7.0
* the prepared war makes use of two properties so that indexing takes place as soon as possible
** {{jspwiki.lucene.initialdelay}} = 0 # this is the amount of seconds JSPWiki will wait before starting the global indexing at startup (defaults to 60)
** {{jspwiki.lucene.indexdelay}} = 1 # this is the amount of seconds the lucene indexer thread waits before indexing changes (defaults to 5)
** maybe these properties are worth playing with?
HTH
> Lucene Index not updated on edits/new page
> ------------------------------------------
>
> Key: JSPWIKI-1131
> URL: https://issues.apache.org/jira/browse/JSPWIKI-1131
> Project: JSPWiki
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.11.0-M7
> Environment: * Debian 10
> * Tomcat 9: 9.0.31-1~deb10u2
> * OpenJDK-JRE 11: 11.0.7+10-3~deb10u1
> * JSPWiki 2.11.0-M7
> Reporter: FP
> Priority: Critical
> Fix For: 2.11.0-M8
>
> Attachments: exception.txt, illegal-page-name.txt
>
>
> It seems that the lucene search index is not updated when a user edits an existing page or creates a new page. In both cases, the page is not found when someone searches for it.
> Search works as expected when:
> * Tomcat is stopped
> * The files in the {{lucene}} directory are removed
> * Tomcat is started
> * Wait until the Lucene Indexer thread finishes reindexing
> The following exception occurs when a page is edited (full stack trace attached):
> {{java.io.NotSerializableException: org.apache.wiki.WikiContext}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)