I think that would be a good idea. That's more or less what I ended up
doing myself.
Gary
On 12/8/2021 2:27 PM, Juan Pablo Santos Rodríguez wrote:
Hi Gary,
Glad that you were able to make it work :-)
To avoid this kind of situations onwards I was thinking of tweaking
the workDir property
Hi Gary,
Glad that you were able to make it work :-)
To avoid this kind of situations onwards I was thinking of tweaking the
workDir property so that the generated work dir would be calculated as
jspwiki.workDir + '/' + jspwiki.applicationName. Did you set up this last
property in any of your 3
Juan Pablo,
I found a folder named "lucene" in the working directory and delete
that, then stopped and restarted Wildfly. No change, sadly, in either
the search or WikiCategory.
Yes, I will gladly add our site once we get this working.
Gary
On 12/7/2021 2:27 PM, Juan Pablo Santos Rodríguez
Yes, that was it. When I redefined the working directory on each of the
JSPWiki instances to separate directories, everything started working.
Gary
On 12/7/2021 11:05 PM, Gary Kephart wrote:
A closer look at Wildfly's server log showed this:
2021-12-07 14:37:35,215 ERROR
A closer look at Wildfly's server log showed this:
2021-12-07 14:37:35,215 ERROR
[org.apache.wiki.search.LuceneSearchProvider] (JSPWiki Lucene Indexer)
Unable to start lucene: java.nio.channels.OverlappingFileLockException
at
Hi Gary,
lucene index files are stored inside a dir called 'lucene-dir' inside
JSPWiki's working directory (/tmp or c:\temp if you haven't customised
the jspwiki.workDir property inside your jspwiki[-custom]-properties
file). Latest JSPWiki bundles lucene-backwards-codecs, which are
supposed to
Juan,
Attached is a log file. I don't see anything unusual like an exception
being thrown. I'm unfamiliar with Lucene beyond knowing it's for
searching. But it is interesting that the site search is also not
working. It returns no search results. I'm not sure which files are the
Lucene index
