You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jspwiki.apache.org by Dave Koelmeyer <da...@davekoelmeyer.co.nz> on 2013/02/23 12:52:47 UTC
Quick search has stopped working
Hi All,
Yesterday it worked, today it has stopped working. When typing in a
keyword in my JSPWiki search bar, I would usually have dozens of search
hits returned dynamically. This has stopped working altogether, and
nothing is returned dynamically. I was using JSPWiki 2.8.3, upgrading to
2.9.0 hasn't changed the behaviour (has fixed a couple of other bugs
though which is lovely). I'm using GlassFish 3.1.2.2 with JDK 6 update
37, all on OpenIndiana oi_151a7.
Any pointers to what might have gone wrong here?
Cheers,
Dave
--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
Re: Quick search has stopped working
Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
On 21/03/13 09:11 AM, Harry Metske wrote:
> Dave,
>
> can you try the latest (2.9.1-svn-31) build ?
>
> regards,
> Harry
Eureka! That's fixed it. Quick search results are back to what they
should be :)
Thanks very much Harry (and Dirk and Juan Pablo too) for all the help.
Cheers,
Dave
--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
Re: Quick search has stopped working
Posted by Harry Metske <ha...@gmail.com>.
Dave,
can you try the latest (2.9.1-svn-31) build ?
regards,
Harry
On 19 March 2013 18:42, Harry Metske <ha...@gmail.com> wrote:
> (just te be sure) did you clean your browser cache and refreshed the page?
> And myself , I always clean tomcat's work directory to get rid of compiled
> JSP's.
>
> About the 2.9 release, that was a bit of a misunderstanding I guess.
> We released 2.9.0, the first official apache release, that one can be
> downloaded (also binaries).
>
> regards,
> Harry
>
>
> On 19 March 2013 07:01, Dave Koelmeyer <dave.koelmeyer@davekoelmeyer.co.nz
> > wrote:
>
>> On 19/03/13 3:00 AM, Harry Metske wrote:
>>
>>> Dave,
>>>
>>> there is a nightly build by Jenkins:
>>> https://builds.apache.org/job/**JSPWiki/<https://builds.apache.org/job/JSPWiki/>,
>>> but the resulting binaries are
>>>
>>> not on a downloadable location AFAIK.
>>> You can always check out the sources and run "ant war" on it.
>>>
>> Hi Harry,
>>
>> Thanks for this - I've built the WAR from source as per your
>> instructions, and installed it in GlassFish. The JSPWiki version is
>> correctly reported as version 2.9.1-svn-30. Interestingly however now no
>> quick search results are returned at all. "Normal" search results though
>> are back to what they should be:
>>
>> http://ubuntuone.com/**2JCl4w2z7gHjajGBnqx2NY<http://ubuntuone.com/2JCl4w2z7gHjajGBnqx2NY>
>>
>> I have cleared the Lucene cache and restarted the app server but there is
>> no change in behaviour. I'm also not seeing any JS errors in the Firefox
>> web console.
>>
>>
>> Anyway, the same way as you got the "previous" 2.9 release ?
>>>
>>
>> Unless I'm missing something, both http://www.jspwiki.org/wiki/**
>> JSPWikiDownload#section-**JSPWikiDownload-**CurrentStableRelease2.8.41<http://www.jspwiki.org/wiki/JSPWikiDownload#section-JSPWikiDownload-CurrentStableRelease2.8.41>and
>> http://incubator.apache.org/**jspwiki/general/downloads.html<http://incubator.apache.org/jspwiki/general/downloads.html>are pointing to version 2.9.0.
>>
>>
>> Cheers,
>> Dave
>>
>> --
>> Dave Koelmeyer
>> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz>
>>
>>
>
Re: Quick search has stopped working
Posted by Harry Metske <ha...@gmail.com>.
(just te be sure) did you clean your browser cache and refreshed the page?
And myself , I always clean tomcat's work directory to get rid of compiled
JSP's.
About the 2.9 release, that was a bit of a misunderstanding I guess.
We released 2.9.0, the first official apache release, that one can be
downloaded (also binaries).
regards,
Harry
On 19 March 2013 07:01, Dave Koelmeyer
<da...@davekoelmeyer.co.nz>wrote:
> On 19/03/13 3:00 AM, Harry Metske wrote:
>
>> Dave,
>>
>> there is a nightly build by Jenkins:
>> https://builds.apache.org/job/**JSPWiki/<https://builds.apache.org/job/JSPWiki/>,
>> but the resulting binaries are
>>
>> not on a downloadable location AFAIK.
>> You can always check out the sources and run "ant war" on it.
>>
> Hi Harry,
>
> Thanks for this - I've built the WAR from source as per your instructions,
> and installed it in GlassFish. The JSPWiki version is correctly reported as
> version 2.9.1-svn-30. Interestingly however now no quick search results are
> returned at all. "Normal" search results though are back to what they
> should be:
>
> http://ubuntuone.com/**2JCl4w2z7gHjajGBnqx2NY<http://ubuntuone.com/2JCl4w2z7gHjajGBnqx2NY>
>
> I have cleared the Lucene cache and restarted the app server but there is
> no change in behaviour. I'm also not seeing any JS errors in the Firefox
> web console.
>
>
> Anyway, the same way as you got the "previous" 2.9 release ?
>>
>
> Unless I'm missing something, both http://www.jspwiki.org/wiki/**
> JSPWikiDownload#section-**JSPWikiDownload-**CurrentStableRelease2.8.41<http://www.jspwiki.org/wiki/JSPWikiDownload#section-JSPWikiDownload-CurrentStableRelease2.8.41>and
> http://incubator.apache.org/**jspwiki/general/downloads.html<http://incubator.apache.org/jspwiki/general/downloads.html>are pointing to version 2.9.0.
>
>
> Cheers,
> Dave
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz>
>
>
Re: Quick search has stopped working
Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
On 19/03/13 3:00 AM, Harry Metske wrote:
> Dave,
>
> there is a nightly build by Jenkins:
> https://builds.apache.org/job/JSPWiki/, but the resulting binaries are
> not on a downloadable location AFAIK.
> You can always check out the sources and run "ant war" on it.
Hi Harry,
Thanks for this - I've built the WAR from source as per your
instructions, and installed it in GlassFish. The JSPWiki version is
correctly reported as version 2.9.1-svn-30. Interestingly however now no
quick search results are returned at all. "Normal" search results though
are back to what they should be:
http://ubuntuone.com/2JCl4w2z7gHjajGBnqx2NY
I have cleared the Lucene cache and restarted the app server but there
is no change in behaviour. I'm also not seeing any JS errors in the
Firefox web console.
> Anyway, the same way as you got the "previous" 2.9 release ?
Unless I'm missing something, both
http://www.jspwiki.org/wiki/JSPWikiDownload#section-JSPWikiDownload-CurrentStableRelease2.8.41
and http://incubator.apache.org/jspwiki/general/downloads.html are
pointing to version 2.9.0.
Cheers,
Dave
--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
Re: Quick search has stopped working
Posted by Harry Metske <ha...@gmail.com>.
Dave,
there is a nightly build by Jenkins:
https://builds.apache.org/job/JSPWiki/, but the resulting binaries are
not on a downloadable location AFAIK.
You can always check out the sources and run "ant war" on it.
Anyway, the same way as you got the "previous" 2.9 release ?
kind regards,
Harry
On 18 March 2013 09:08, Dave Koelmeyer
<da...@davekoelmeyer.co.nz>wrote:
> On 18/03/13 07:32 AM, Harry Metske wrote:
>
>> Dave,
>>
>> can you test with 2.9.1-svn-30, that should have fixed the issue.
>>
>
> Hi Harry,
>
> Awesome, thanks. Do you know if there is a nightly build of this
> somewhere?(http://www.jspwiki.**org/wiki/JSPWikiDownload#**
> section-JSPWikiDownload-**TheLatestCuttingEdgeCodeOfJSPW**iki<http://www.jspwiki.org/wiki/JSPWikiDownload#section-JSPWikiDownload-TheLatestCuttingEdgeCodeOfJSPWiki>seems out of date).
>
>
> Cheers,
> Dave
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz>
>
>
>
>
>>
>> On 17 March 2013 15:34, Harry Metske <ha...@gmail.com> wrote:
>>
>> in the 2.9 wiki, the maximum number of hits you get is 3, no matter what
>>> you are searching for.
>>> I have to dig a bit deeper, but the MAX_FRAGMENTS also has the value of
>>> 3 .
>>>
>>> regards,
>>> Harry
>>>
>>>
>>> On 17 March 2013 15:19, Harry Metske <ha...@gmail.com> wrote:
>>>
>>> I have setup two test wiki's from scratch, a 2.8 and a 2.9. (both
>>>> running
>>>> in the same tomcat 7.0.37 instance with openjdk 1.7.0_15).
>>>>
>>>> I dumped my personal (250 page) wiki content into both of them, and did
>>>> some random searches on both.
>>>> Simply searching for the word "file" gives completely different results
>>>> (68 versus 3 hits).
>>>> This must be something with the new Lucene I guess.
>>>>
>>>> Can you file a JIRA issue on this ?, we have to investigate this
>>>> further.
>>>>
>>>> kind regards,
>>>> Harry
>>>>
>>>>
>>>> On 17 March 2013 12:41, Dave Koelmeyer <
>>>> dave.koelmeyer@davekoelmeyer.**co.nz<da...@davekoelmeyer.co.nz>>
>>>> wrote:
>>>>
>>>> On 18/03/13 12:29 AM, Florian Holeczek wrote:
>>>>>
>>>>> Hi again,
>>>>>>
>>>>>> Thanks, but I've tried all this and there has been no change in
>>>>>>
>>>>>>> behaviour. Also, I've got two instances of JSPWiki running on the
>>>>>>> same host
>>>>>>> platform, and I'm not seeing this with JSPWiki 2.8.3.
>>>>>>>
>>>>>>> which JDK version are you using? I remember the first Oracle JDK 7
>>>>>> had
>>>>>> some overly aggressive optimization which caused Lucene not to work
>>>>>> properly.
>>>>>> Did you enable the debug logging before index rebuild? I'd expect to
>>>>>> see some Exception which may then cause the index build to stop.
>>>>>>
>>>>>> Hi Florian,
>>>>>
>>>>> I'm on JDK 6 update 37. I'll erase the Lucene cache and have another
>>>>> look at the logs - perhaps I missed something.
>>>>>
>>>>>
>>>>> Cheers,
>>>>> Dave
>>>>>
>>>>>
>>>>>
>
Re: Quick search has stopped working
Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
On 18/03/13 07:32 AM, Harry Metske wrote:
> Dave,
>
> can you test with 2.9.1-svn-30, that should have fixed the issue.
Hi Harry,
Awesome, thanks. Do you know if there is a nightly build of this
somewhere?(http://www.jspwiki.org/wiki/JSPWikiDownload#section-JSPWikiDownload-TheLatestCuttingEdgeCodeOfJSPWiki
seems out of date).
Cheers,
Dave
--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
>
>
> On 17 March 2013 15:34, Harry Metske <ha...@gmail.com> wrote:
>
>> in the 2.9 wiki, the maximum number of hits you get is 3, no matter what
>> you are searching for.
>> I have to dig a bit deeper, but the MAX_FRAGMENTS also has the value of 3 .
>>
>> regards,
>> Harry
>>
>>
>> On 17 March 2013 15:19, Harry Metske <ha...@gmail.com> wrote:
>>
>>> I have setup two test wiki's from scratch, a 2.8 and a 2.9. (both running
>>> in the same tomcat 7.0.37 instance with openjdk 1.7.0_15).
>>>
>>> I dumped my personal (250 page) wiki content into both of them, and did
>>> some random searches on both.
>>> Simply searching for the word "file" gives completely different results
>>> (68 versus 3 hits).
>>> This must be something with the new Lucene I guess.
>>>
>>> Can you file a JIRA issue on this ?, we have to investigate this further.
>>>
>>> kind regards,
>>> Harry
>>>
>>>
>>> On 17 March 2013 12:41, Dave Koelmeyer <
>>> dave.koelmeyer@davekoelmeyer.co.nz> wrote:
>>>
>>>> On 18/03/13 12:29 AM, Florian Holeczek wrote:
>>>>
>>>>> Hi again,
>>>>>
>>>>> Thanks, but I've tried all this and there has been no change in
>>>>>> behaviour. Also, I've got two instances of JSPWiki running on the same host
>>>>>> platform, and I'm not seeing this with JSPWiki 2.8.3.
>>>>>>
>>>>> which JDK version are you using? I remember the first Oracle JDK 7 had
>>>>> some overly aggressive optimization which caused Lucene not to work
>>>>> properly.
>>>>> Did you enable the debug logging before index rebuild? I'd expect to
>>>>> see some Exception which may then cause the index build to stop.
>>>>>
>>>> Hi Florian,
>>>>
>>>> I'm on JDK 6 update 37. I'll erase the Lucene cache and have another
>>>> look at the logs - perhaps I missed something.
>>>>
>>>>
>>>> Cheers,
>>>> Dave
>>>>
>>>>
Re: Quick search has stopped working
Posted by Harry Metske <ha...@gmail.com>.
Dave,
can you test with 2.9.1-svn-30, that should have fixed the issue.
regards,
Harry
On 17 March 2013 15:34, Harry Metske <ha...@gmail.com> wrote:
> in the 2.9 wiki, the maximum number of hits you get is 3, no matter what
> you are searching for.
> I have to dig a bit deeper, but the MAX_FRAGMENTS also has the value of 3 .
>
> regards,
> Harry
>
>
> On 17 March 2013 15:19, Harry Metske <ha...@gmail.com> wrote:
>
>> I have setup two test wiki's from scratch, a 2.8 and a 2.9. (both running
>> in the same tomcat 7.0.37 instance with openjdk 1.7.0_15).
>>
>> I dumped my personal (250 page) wiki content into both of them, and did
>> some random searches on both.
>> Simply searching for the word "file" gives completely different results
>> (68 versus 3 hits).
>> This must be something with the new Lucene I guess.
>>
>> Can you file a JIRA issue on this ?, we have to investigate this further.
>>
>> kind regards,
>> Harry
>>
>>
>> On 17 March 2013 12:41, Dave Koelmeyer <
>> dave.koelmeyer@davekoelmeyer.co.nz> wrote:
>>
>>> On 18/03/13 12:29 AM, Florian Holeczek wrote:
>>>
>>>> Hi again,
>>>>
>>>> Thanks, but I've tried all this and there has been no change in
>>>>> behaviour. Also, I've got two instances of JSPWiki running on the same host
>>>>> platform, and I'm not seeing this with JSPWiki 2.8.3.
>>>>>
>>>>
>>>> which JDK version are you using? I remember the first Oracle JDK 7 had
>>>> some overly aggressive optimization which caused Lucene not to work
>>>> properly.
>>>> Did you enable the debug logging before index rebuild? I'd expect to
>>>> see some Exception which may then cause the index build to stop.
>>>>
>>>
>>> Hi Florian,
>>>
>>> I'm on JDK 6 update 37. I'll erase the Lucene cache and have another
>>> look at the logs - perhaps I missed something.
>>>
>>>
>>> Cheers,
>>> Dave
>>>
>>> --
>>> Dave Koelmeyer
>>> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz>
>>>
>>>
>>
>
Re: Quick search has stopped working
Posted by Harry Metske <ha...@gmail.com>.
in the 2.9 wiki, the maximum number of hits you get is 3, no matter what
you are searching for.
I have to dig a bit deeper, but the MAX_FRAGMENTS also has the value of 3 .
regards,
Harry
On 17 March 2013 15:19, Harry Metske <ha...@gmail.com> wrote:
> I have setup two test wiki's from scratch, a 2.8 and a 2.9. (both running
> in the same tomcat 7.0.37 instance with openjdk 1.7.0_15).
>
> I dumped my personal (250 page) wiki content into both of them, and did
> some random searches on both.
> Simply searching for the word "file" gives completely different results
> (68 versus 3 hits).
> This must be something with the new Lucene I guess.
>
> Can you file a JIRA issue on this ?, we have to investigate this further.
>
> kind regards,
> Harry
>
>
> On 17 March 2013 12:41, Dave Koelmeyer <dave.koelmeyer@davekoelmeyer.co.nz
> > wrote:
>
>> On 18/03/13 12:29 AM, Florian Holeczek wrote:
>>
>>> Hi again,
>>>
>>> Thanks, but I've tried all this and there has been no change in
>>>> behaviour. Also, I've got two instances of JSPWiki running on the same host
>>>> platform, and I'm not seeing this with JSPWiki 2.8.3.
>>>>
>>>
>>> which JDK version are you using? I remember the first Oracle JDK 7 had
>>> some overly aggressive optimization which caused Lucene not to work
>>> properly.
>>> Did you enable the debug logging before index rebuild? I'd expect to see
>>> some Exception which may then cause the index build to stop.
>>>
>>
>> Hi Florian,
>>
>> I'm on JDK 6 update 37. I'll erase the Lucene cache and have another look
>> at the logs - perhaps I missed something.
>>
>>
>> Cheers,
>> Dave
>>
>> --
>> Dave Koelmeyer
>> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz>
>>
>>
>
Re: Quick search has stopped working
Posted by Harry Metske <ha...@gmail.com>.
I have setup two test wiki's from scratch, a 2.8 and a 2.9. (both running
in the same tomcat 7.0.37 instance with openjdk 1.7.0_15).
I dumped my personal (250 page) wiki content into both of them, and did
some random searches on both.
Simply searching for the word "file" gives completely different results (68
versus 3 hits).
This must be something with the new Lucene I guess.
Can you file a JIRA issue on this ?, we have to investigate this further.
kind regards,
Harry
On 17 March 2013 12:41, Dave Koelmeyer
<da...@davekoelmeyer.co.nz>wrote:
> On 18/03/13 12:29 AM, Florian Holeczek wrote:
>
>> Hi again,
>>
>> Thanks, but I've tried all this and there has been no change in
>>> behaviour. Also, I've got two instances of JSPWiki running on the same host
>>> platform, and I'm not seeing this with JSPWiki 2.8.3.
>>>
>>
>> which JDK version are you using? I remember the first Oracle JDK 7 had
>> some overly aggressive optimization which caused Lucene not to work
>> properly.
>> Did you enable the debug logging before index rebuild? I'd expect to see
>> some Exception which may then cause the index build to stop.
>>
>
> Hi Florian,
>
> I'm on JDK 6 update 37. I'll erase the Lucene cache and have another look
> at the logs - perhaps I missed something.
>
>
> Cheers,
> Dave
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz>
>
>
Re: Quick search has stopped working
Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
On 18/03/13 12:29 AM, Florian Holeczek wrote:
> Hi again,
>
>> Thanks, but I've tried all this and there has been no change in
>> behaviour. Also, I've got two instances of JSPWiki running on the
>> same host platform, and I'm not seeing this with JSPWiki 2.8.3.
>
> which JDK version are you using? I remember the first Oracle JDK 7 had
> some overly aggressive optimization which caused Lucene not to work
> properly.
> Did you enable the debug logging before index rebuild? I'd expect to
> see some Exception which may then cause the index build to stop.
Hi Florian,
I'm on JDK 6 update 37. I'll erase the Lucene cache and have another
look at the logs - perhaps I missed something.
Cheers,
Dave
--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
Re: Quick search has stopped working
Posted by Florian Holeczek <fl...@holeczek.de>.
Hi again,
> Thanks, but I've tried all this and there has been no change in behaviour. Also, I've got two instances of JSPWiki running on the same host platform, and I'm not seeing this with JSPWiki 2.8.3.
which JDK version are you using? I remember the first Oracle JDK 7 had some overly aggressive optimization which caused Lucene not to work properly.
Did you enable the debug logging before index rebuild? I'd expect to see some Exception which may then cause the index build to stop.
Regards
Florian
Re: Quick search has stopped working
Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
On 17/03/13 11:01 PM, Florian Holeczek wrote:
> Hi Dave!
>
>>> is it only the Quick search which isn't working, or any search
>>> functionality at all?
>>> Have you tried yet to rebuild the Lucene index for your wiki?
>
>> It is actually both, looking at it. I'm seeing a greatly reduced
>> number of returned search results (and quick search results)
>> apparently compared to versions of JSPWiki earlier than 2.9.0. I've
>> been clearing out the contents of my JSPWiki working directory which
>> is where I understand the Lucene cache to be put, unless there is
>> another method of rebuilding the index. I can post a video
>> screencapture of what I'm seeing if it helps at all.
>
> OK, then I'm pretty sure that we're simply dealing with a corrupted
> index here.
> Yes, the index is stored under <workdir>/lucene. So, wiping the
> workdir while JSPWiki is down and then restarting JSPWiki will lead to
> generation of a new index sooner or later. This is normally the way to
> go when dealing with a corrupted index. Updating the index can be done
> via JMX, too, AFAIR.
Hi Florian.
Thanks, but I've tried all this and there has been no change in
behaviour. Also, I've got two instances of JSPWiki running on the same
host platform, and I'm not seeing this with JSPWiki 2.8.3.
Cheers,
Dave
--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
Re: Quick search has stopped working
Posted by Florian Holeczek <fl...@holeczek.de>.
Hi Dave!
>> is it only the Quick search which isn't working, or any search functionality at all?
>> Have you tried yet to rebuild the Lucene index for your wiki?
> It is actually both, looking at it. I'm seeing a greatly reduced number of returned search results (and quick search results) apparently compared to versions of JSPWiki earlier than 2.9.0. I've been clearing out the contents of my JSPWiki working directory which is where I understand the Lucene cache to be put, unless there is another method of rebuilding the index. I can post a video screencapture of what I'm seeing if it helps at all.
OK, then I'm pretty sure that we're simply dealing with a corrupted index here.
Yes, the index is stored under <workdir>/lucene. So, wiping the workdir while JSPWiki is down and then restarting JSPWiki will lead to generation of a new index sooner or later. This is normally the way to go when dealing with a corrupted index. Updating the index can be done via JMX, too, AFAIR.
Regards
Florian
Re: Quick search has stopped working
Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
On 17/03/13 10:09 PM, Florian Holeczek wrote:
> Hi Dave,
>
> is it only the Quick search which isn't working, or any search
> functionality at all?
> Have you tried yet to rebuild the Lucene index for your wiki?
>
Hi Florian,
It is actually both, looking at it. I'm seeing a greatly reduced number
of returned search results (and quick search results) apparently
compared to versions of JSPWiki earlier than 2.9.0. I've been clearing
out the contents of my JSPWiki working directory which is where I
understand the Lucene cache to be put, unless there is another method of
rebuilding the index. I can post a video screencapture of what I'm
seeing if it helps at all.
Cheers,
Dave
>
> On 17.03.2013 09:55, Dave Koelmeyer wrote:
>> Hi Juan Pablo,
>>
>> On 17/03/13 02:53 AM, Juan Pablo Santos Rodríguez wrote:
>>> could you try switching the StandardAnalyzer to
>>> org.apache.lucene.analysis.standard.ClassicAnalyzer? from the javadocs
>>> "ClassicAnalyzer was named StandardAnalyzer in Lucene versions prior to
>>> 3.1. As of 3.1,
>>> StandardAnalyzer<http://lucene.apache.org/core/3_6_0/api/core/org/apache/lucene/analysis/standard/StandardAnalyzer.html>implements
>>>
>>> Unicode text segmentation, as specified by UAX#29" so maybe that
>>> could explain the search differences between versions
>> I've stopped the GlassFish domain, deleted the Lucene caches, made
>> this change in the jspwiki.properties file and started the domain up
>> again, and there is no change in behaviour. I still only get three or
>> so quick search results, vs ~20 for the same search query on JSPWiki
>> 2.8.3.
>>
>>> I'm unable to look at this right now, but I'll try to do it next week
>>
>> That would be great. If I stumble across anything further until then
>> I'll be sure to let you know.
>>
>> Cheers,
>> Dave
>>
--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
Re: Quick search has stopped working
Posted by Florian Holeczek <fl...@holeczek.de>.
Hi Dave,
is it only the Quick search which isn't working, or any search functionality at all?
Have you tried yet to rebuild the Lucene index for your wiki?
Regards
Florian
On 17.03.2013 09:55, Dave Koelmeyer wrote:
> Hi Juan Pablo,
>
> On 17/03/13 02:53 AM, Juan Pablo Santos Rodríguez wrote:
>> could you try switching the StandardAnalyzer to
>> org.apache.lucene.analysis.standard.ClassicAnalyzer? from the javadocs
>> "ClassicAnalyzer was named StandardAnalyzer in Lucene versions prior to
>> 3.1. As of 3.1,
>> StandardAnalyzer<http://lucene.apache.org/core/3_6_0/api/core/org/apache/lucene/analysis/standard/StandardAnalyzer.html>implements
>> Unicode text segmentation, as specified by UAX#29" so maybe that
>> could explain the search differences between versions
> I've stopped the GlassFish domain, deleted the Lucene caches, made this change in the jspwiki.properties file and started the domain up again, and there is no change in behaviour. I still only get three or so quick search results, vs ~20 for the same search query on JSPWiki 2.8.3.
>
>> I'm unable to look at this right now, but I'll try to do it next week
>
> That would be great. If I stumble across anything further until then I'll be sure to let you know.
>
> Cheers,
> Dave
>
Re: Quick search has stopped working
Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
Hi Juan Pablo,
On 17/03/13 02:53 AM, Juan Pablo Santos Rodríguez wrote:
> could you try switching the StandardAnalyzer to
> org.apache.lucene.analysis.standard.ClassicAnalyzer? from the javadocs
> "ClassicAnalyzer was named StandardAnalyzer in Lucene versions prior to
> 3.1. As of 3.1,
> StandardAnalyzer<http://lucene.apache.org/core/3_6_0/api/core/org/apache/lucene/analysis/standard/StandardAnalyzer.html>implements
> Unicode text segmentation, as specified by UAX#29" so maybe that
> could explain the search differences between versions
I've stopped the GlassFish domain, deleted the Lucene caches, made this
change in the jspwiki.properties file and started the domain up again,
and there is no change in behaviour. I still only get three or so quick
search results, vs ~20 for the same search query on JSPWiki 2.8.3.
> I'm unable to look at this right now, but I'll try to do it next week
That would be great. If I stumble across anything further until then
I'll be sure to let you know.
Cheers,
Dave
--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
>
> On Sat, Mar 16, 2013 at 1:49 PM, Dave Koelmeyer <
> dave.koelmeyer@davekoelmeyer.co.nz> wrote:
>
>> On 16/03/13 12:47 AM, Dave Koelmeyer wrote:
>>
>>> On 13/03/13 08:56 AM, Juan Pablo Santos Rodríguez wrote:
>>>
>>>> Lucene was updated from 2.0.0 to 3.6.0 in 2.9.0-svn-3 (
>>>> https://issues.apache.org/**jira/browse/JSPWIKI-729<https://issues.apache.org/jira/browse/JSPWIKI-729>),
>>>> and the code rewritten
>>>> to use the new API, but essentially it has the same behaviour as before,
>>>> it
>>>> passes the same unit tests. Could you please set the logger level to
>>>> debug
>>>> to see if something pops out from the log file?
>>>>
>>>> I'm assuming you're using the LuceneSearchProvider in your
>>>> jspwiki.properties and the StandardAnalyzer (these are the default
>>>> values)
>>>>
>>>>
>>> Thanks for the reply, I will do that and post any relevant output
>>> shortly. Just for information I have created a second GlassFish domain
>>> using the same host OS, GlassFish and Java versions, but using JSPWiki
>>> 2.8.3. Pointing JSPWiki 2.8.3 to a copy of the same content repository used
>>> with JSPWiki 2.9.0 and performing a search I get the expected number of
>>> quick search results. Contrary to what I said in my original post on this
>>> topic I may well have first observed the behaviour after upgrading to 2.9.0.
>>>
>>>
>> Hi All,
>>
>> Well I've enabled debug output (according to http://doc.jspwiki.org/2.4/**
>> wiki/JSPWiki.properties#**section-JSPWiki.properties-**
>> TurningOnFullDEBUGMode<http://doc.jspwiki.org/2.4/wiki/JSPWiki.properties#section-JSPWiki.properties-TurningOnFullDEBUGMode>) and I can't see anything error-wise in either the GlassFish or JSPWiki
>> log files, certainly not anything related to search or Lucene. I've got all
>> Lucene and search values at defaults in jspwiki.properties too, to answer
>> your question.
>>
>> Any other pointers to things to check for? And has anyone else perhaps
>> done an A/B test between JSPWiki 2.9.0 and earlier versions?
>>
>>
>>
Re: Quick search has stopped working
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hi Dave,
could you try switching the StandardAnalyzer to
org.apache.lucene.analysis.standard.ClassicAnalyzer? from the javadocs
"ClassicAnalyzer was named StandardAnalyzer in Lucene versions prior to
3.1. As of 3.1,
StandardAnalyzer<http://lucene.apache.org/core/3_6_0/api/core/org/apache/lucene/analysis/standard/StandardAnalyzer.html>implements
Unicode text segmentation, as specified by UAX#29" so maybe that
could explain the search differences between versions
I'm unable to look at this right now, but I'll try to do it next week
br,
juan pablo
On Sat, Mar 16, 2013 at 1:49 PM, Dave Koelmeyer <
dave.koelmeyer@davekoelmeyer.co.nz> wrote:
> On 16/03/13 12:47 AM, Dave Koelmeyer wrote:
>
>> On 13/03/13 08:56 AM, Juan Pablo Santos Rodríguez wrote:
>>
>>>
>>> Lucene was updated from 2.0.0 to 3.6.0 in 2.9.0-svn-3 (
>>> https://issues.apache.org/**jira/browse/JSPWIKI-729<https://issues.apache.org/jira/browse/JSPWIKI-729>),
>>> and the code rewritten
>>> to use the new API, but essentially it has the same behaviour as before,
>>> it
>>> passes the same unit tests. Could you please set the logger level to
>>> debug
>>> to see if something pops out from the log file?
>>>
>>> I'm assuming you're using the LuceneSearchProvider in your
>>> jspwiki.properties and the StandardAnalyzer (these are the default
>>> values)
>>>
>>>
>> Thanks for the reply, I will do that and post any relevant output
>> shortly. Just for information I have created a second GlassFish domain
>> using the same host OS, GlassFish and Java versions, but using JSPWiki
>> 2.8.3. Pointing JSPWiki 2.8.3 to a copy of the same content repository used
>> with JSPWiki 2.9.0 and performing a search I get the expected number of
>> quick search results. Contrary to what I said in my original post on this
>> topic I may well have first observed the behaviour after upgrading to 2.9.0.
>>
>>
> Hi All,
>
> Well I've enabled debug output (according to http://doc.jspwiki.org/2.4/**
> wiki/JSPWiki.properties#**section-JSPWiki.properties-**
> TurningOnFullDEBUGMode<http://doc.jspwiki.org/2.4/wiki/JSPWiki.properties#section-JSPWiki.properties-TurningOnFullDEBUGMode>) and I can't see anything error-wise in either the GlassFish or JSPWiki
> log files, certainly not anything related to search or Lucene. I've got all
> Lucene and search values at defaults in jspwiki.properties too, to answer
> your question.
>
> Any other pointers to things to check for? And has anyone else perhaps
> done an A/B test between JSPWiki 2.9.0 and earlier versions?
>
>
> Cheers,
> Dave
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz>
>
>
Re: Quick search has stopped working
Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
On 16/03/13 12:47 AM, Dave Koelmeyer wrote:
> On 13/03/13 08:56 AM, Juan Pablo Santos Rodríguez wrote:
>>
>> Lucene was updated from 2.0.0 to 3.6.0 in 2.9.0-svn-3 (
>> https://issues.apache.org/jira/browse/JSPWIKI-729), and the code
>> rewritten
>> to use the new API, but essentially it has the same behaviour as
>> before, it
>> passes the same unit tests. Could you please set the logger level to
>> debug
>> to see if something pops out from the log file?
>>
>> I'm assuming you're using the LuceneSearchProvider in your
>> jspwiki.properties and the StandardAnalyzer (these are the default
>> values)
>>
>
> Thanks for the reply, I will do that and post any relevant output
> shortly. Just for information I have created a second GlassFish domain
> using the same host OS, GlassFish and Java versions, but using JSPWiki
> 2.8.3. Pointing JSPWiki 2.8.3 to a copy of the same content repository
> used with JSPWiki 2.9.0 and performing a search I get the expected
> number of quick search results. Contrary to what I said in my original
> post on this topic I may well have first observed the behaviour after
> upgrading to 2.9.0.
>
Hi All,
Well I've enabled debug output (according to
http://doc.jspwiki.org/2.4/wiki/JSPWiki.properties#section-JSPWiki.properties-TurningOnFullDEBUGMode)
and I can't see anything error-wise in either the GlassFish or JSPWiki
log files, certainly not anything related to search or Lucene. I've got
all Lucene and search values at defaults in jspwiki.properties too, to
answer your question.
Any other pointers to things to check for? And has anyone else perhaps
done an A/B test between JSPWiki 2.9.0 and earlier versions?
Cheers,
Dave
--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
Re: Quick search has stopped working
Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
On 13/03/13 08:56 AM, Juan Pablo Santos Rodríguez wrote:
> Hi Dave,
>
> Lucene was updated from 2.0.0 to 3.6.0 in 2.9.0-svn-3 (
> https://issues.apache.org/jira/browse/JSPWIKI-729), and the code rewritten
> to use the new API, but essentially it has the same behaviour as before, it
> passes the same unit tests. Could you please set the logger level to debug
> to see if something pops out from the log file?
>
> I'm assuming you're using the LuceneSearchProvider in your
> jspwiki.properties and the StandardAnalyzer (these are the default values)
>
> thx,
> juan pablo
Hi Juan Pablo,
Thanks for the reply, I will do that and post any relevant output
shortly. Just for information I have created a second GlassFish domain
using the same host OS, GlassFish and Java versions, but using JSPWiki
2.8.3. Pointing JSPWiki 2.8.3 to a copy of the same content repository
used with JSPWiki 2.9.0 and performing a search I get the expected
number of quick search results. Contrary to what I said in my original
post on this topic I may well have first observed the behaviour after
upgrading to 2.9.0.
Cheers,
Dave
--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
>
> On Sat, Mar 9, 2013 at 7:48 AM, Dave Koelmeyer <
> dave.koelmeyer@davekoelmeyer.co.nz> wrote:
>
>> On 24/02/13 10:37 PM, Dirk Frederickx wrote:
>>
>>> You may want to delete the lucene indexes, and restart jspwiki. (so it
>>> will
>>> build new search indexes)
>>>
>>
>> Hi Dirk,
>>
>> Thanks for your reply - I've stopped the domain, deleted the entire
>> contents of the JSPWiki working directory and fired it back up again. It
>> doesn't look like there is a change in behaviour however.
>>
>> I've got a screen grab here: http://ubuntuone.com/**5EVUvzZx9pMd52pheDPkbB<http://ubuntuone.com/5EVUvzZx9pMd52pheDPkbB>
>> Top right is what I'm seeing presently. Bottom left is a historical screen
>> grab, and you can see for the same search term the difference in returned
>> results. Differences between the two are newer versions of JSPWiki,
>> GlassFish and Java, and a heavily customised theme.
>>
>> Any other ideas would be awesome.
>>
>>
>>>
>>>
>>> On Sun, Feb 24, 2013 at 8:54 AM, Dave Koelmeyer <
>>> dave.koelmeyer@davekoelmeyer.**co.nz <da...@davekoelmeyer.co.nz>>
>>> wrote:
>>>
>>> On 24/02/13 11:32 AM, Dirk Frederickx wrote:
>>>> Dave,
>>>>> Can you check the javascript console of the browser ? ( in chrome,
>>>>> Tools
>>>>> => Javascript Console)
>>>>>
>>>>> So you can identify if this is a browser/js issue (eg javascript
>>>>> routines
>>>>> not loaded?) or server issue (eg no response on the ajax search
>>>>> queries)
>>>>>
>>>>>
>>>>> dirk
>>>>>
>>>>> Hi Dirk,
>>>> Thanks for the reply. I've checked with a variety of browsers and no
>>>> JavaScript errors are logged to the web console at all.
>>>>
>>>> Strangely, I've noticed I do actually receive search results for some
>>>> queries - but at maximum only four total (where as in the very recent
>>>> past
>>>> I've had over a dozen for the same search query). I thought perhaps this
>>>> might be a cache memory issue, and reading through the docs I see that
>>>> it's
>>>> best to have the jspwiki.workDir value explicitly set in
>>>> jspwiki.properties
>>>> ("The working directory is used to cache things like Lucene search") -
>>>> I've
>>>> done this and restarted the app server but with no change in behaviour.
>>>>
>>>> Could this behaviour be related to the size of my wiki? It has probably
>>>> several hundred entries at present and in total the content size is
>>>> 170MB.
>>>> If anything has changed it's been the content uploaded to the wiki, and
>>>> not
>>>> anything else to my knowledge.
>>>>
>>>>
>>>>
>>>>
>>>> Hi All,
>>>>
>>>>> Yesterday it worked, today it has stopped working. When typing in a
>>>>>> keyword in my JSPWiki search bar, I would usually have dozens of search
>>>>>> hits returned dynamically. This has stopped working altogether, and
>>>>>> nothing
>>>>>> is returned dynamically. I was using JSPWiki 2.8.3, upgrading to 2.9.0
>>>>>> hasn't changed the behaviour (has fixed a couple of other bugs though
>>>>>> which
>>>>>> is lovely). I'm using GlassFish 3.1.2.2 with JDK 6 update 37, all on
>>>>>> OpenIndiana oi_151a7.
>>>>>>
>>>>>> Any pointers to what might have gone wrong here?
>>>>>>
>>>>>>
Re: Quick search has stopped working
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hi Dave,
Lucene was updated from 2.0.0 to 3.6.0 in 2.9.0-svn-3 (
https://issues.apache.org/jira/browse/JSPWIKI-729), and the code rewritten
to use the new API, but essentially it has the same behaviour as before, it
passes the same unit tests. Could you please set the logger level to debug
to see if something pops out from the log file?
I'm assuming you're using the LuceneSearchProvider in your
jspwiki.properties and the StandardAnalyzer (these are the default values)
thx,
juan pablo
On Sat, Mar 9, 2013 at 7:48 AM, Dave Koelmeyer <
dave.koelmeyer@davekoelmeyer.co.nz> wrote:
> On 24/02/13 10:37 PM, Dirk Frederickx wrote:
>
>> You may want to delete the lucene indexes, and restart jspwiki. (so it
>> will
>> build new search indexes)
>>
>
>
> Hi Dirk,
>
> Thanks for your reply - I've stopped the domain, deleted the entire
> contents of the JSPWiki working directory and fired it back up again. It
> doesn't look like there is a change in behaviour however.
>
> I've got a screen grab here: http://ubuntuone.com/**5EVUvzZx9pMd52pheDPkbB<http://ubuntuone.com/5EVUvzZx9pMd52pheDPkbB>
> Top right is what I'm seeing presently. Bottom left is a historical screen
> grab, and you can see for the same search term the difference in returned
> results. Differences between the two are newer versions of JSPWiki,
> GlassFish and Java, and a heavily customised theme.
>
> Any other ideas would be awesome.
>
> Cheers,
> Dave
>
>
>
>>
>>
>>
>> On Sun, Feb 24, 2013 at 8:54 AM, Dave Koelmeyer <
>> dave.koelmeyer@davekoelmeyer.**co.nz <da...@davekoelmeyer.co.nz>>
>> wrote:
>>
>> On 24/02/13 11:32 AM, Dirk Frederickx wrote:
>>>
>>> Dave,
>>>>
>>>> Can you check the javascript console of the browser ? ( in chrome,
>>>> Tools
>>>> => Javascript Console)
>>>>
>>>> So you can identify if this is a browser/js issue (eg javascript
>>>> routines
>>>> not loaded?) or server issue (eg no response on the ajax search
>>>> queries)
>>>>
>>>>
>>>> dirk
>>>>
>>>> Hi Dirk,
>>>
>>> Thanks for the reply. I've checked with a variety of browsers and no
>>> JavaScript errors are logged to the web console at all.
>>>
>>> Strangely, I've noticed I do actually receive search results for some
>>> queries - but at maximum only four total (where as in the very recent
>>> past
>>> I've had over a dozen for the same search query). I thought perhaps this
>>> might be a cache memory issue, and reading through the docs I see that
>>> it's
>>> best to have the jspwiki.workDir value explicitly set in
>>> jspwiki.properties
>>> ("The working directory is used to cache things like Lucene search") -
>>> I've
>>> done this and restarted the app server but with no change in behaviour.
>>>
>>> Could this behaviour be related to the size of my wiki? It has probably
>>> several hundred entries at present and in total the content size is
>>> 170MB.
>>> If anything has changed it's been the content uploaded to the wiki, and
>>> not
>>> anything else to my knowledge.
>>>
>>>
>>>
>>>
>>> Hi All,
>>>
>>>> Yesterday it worked, today it has stopped working. When typing in a
>>>>> keyword in my JSPWiki search bar, I would usually have dozens of search
>>>>> hits returned dynamically. This has stopped working altogether, and
>>>>> nothing
>>>>> is returned dynamically. I was using JSPWiki 2.8.3, upgrading to 2.9.0
>>>>> hasn't changed the behaviour (has fixed a couple of other bugs though
>>>>> which
>>>>> is lovely). I'm using GlassFish 3.1.2.2 with JDK 6 update 37, all on
>>>>> OpenIndiana oi_151a7.
>>>>>
>>>>> Any pointers to what might have gone wrong here?
>>>>>
>>>>> Cheers,
>>>>> Dave
>>>>>
>>>>>
>>
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz>
>
>
Re: Quick search has stopped working
Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
On 24/02/13 10:37 PM, Dirk Frederickx wrote:
> You may want to delete the lucene indexes, and restart jspwiki. (so it will
> build new search indexes)
Hi Dirk,
Thanks for your reply - I've stopped the domain, deleted the entire
contents of the JSPWiki working directory and fired it back up again. It
doesn't look like there is a change in behaviour however.
I've got a screen grab here: http://ubuntuone.com/5EVUvzZx9pMd52pheDPkbB
Top right is what I'm seeing presently. Bottom left is a historical
screen grab, and you can see for the same search term the difference in
returned results. Differences between the two are newer versions of
JSPWiki, GlassFish and Java, and a heavily customised theme.
Any other ideas would be awesome.
Cheers,
Dave
>
>
>
>
> On Sun, Feb 24, 2013 at 8:54 AM, Dave Koelmeyer <
> dave.koelmeyer@davekoelmeyer.co.nz> wrote:
>
>> On 24/02/13 11:32 AM, Dirk Frederickx wrote:
>>
>>> Dave,
>>>
>>> Can you check the javascript console of the browser ? ( in chrome, Tools
>>> => Javascript Console)
>>>
>>> So you can identify if this is a browser/js issue (eg javascript routines
>>> not loaded?) or server issue (eg no response on the ajax search queries)
>>>
>>>
>>> dirk
>>>
>> Hi Dirk,
>>
>> Thanks for the reply. I've checked with a variety of browsers and no
>> JavaScript errors are logged to the web console at all.
>>
>> Strangely, I've noticed I do actually receive search results for some
>> queries - but at maximum only four total (where as in the very recent past
>> I've had over a dozen for the same search query). I thought perhaps this
>> might be a cache memory issue, and reading through the docs I see that it's
>> best to have the jspwiki.workDir value explicitly set in jspwiki.properties
>> ("The working directory is used to cache things like Lucene search") - I've
>> done this and restarted the app server but with no change in behaviour.
>>
>> Could this behaviour be related to the size of my wiki? It has probably
>> several hundred entries at present and in total the content size is 170MB.
>> If anything has changed it's been the content uploaded to the wiki, and not
>> anything else to my knowledge.
>>
>>
>>
>>
>> Hi All,
>>>> Yesterday it worked, today it has stopped working. When typing in a
>>>> keyword in my JSPWiki search bar, I would usually have dozens of search
>>>> hits returned dynamically. This has stopped working altogether, and
>>>> nothing
>>>> is returned dynamically. I was using JSPWiki 2.8.3, upgrading to 2.9.0
>>>> hasn't changed the behaviour (has fixed a couple of other bugs though
>>>> which
>>>> is lovely). I'm using GlassFish 3.1.2.2 with JDK 6 update 37, all on
>>>> OpenIndiana oi_151a7.
>>>>
>>>> Any pointers to what might have gone wrong here?
>>>>
>>>> Cheers,
>>>> Dave
>>>>
>
--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
Re: Quick search has stopped working
Posted by Dirk Frederickx <di...@gmail.com>.
Dave,
You may want to delete the lucene indexes, and restart jspwiki. (so it will
build new search indexes)
dirk
On Sun, Feb 24, 2013 at 8:54 AM, Dave Koelmeyer <
dave.koelmeyer@davekoelmeyer.co.nz> wrote:
> On 24/02/13 11:32 AM, Dirk Frederickx wrote:
>
>> Dave,
>>
>> Can you check the javascript console of the browser ? ( in chrome, Tools
>> => Javascript Console)
>>
>> So you can identify if this is a browser/js issue (eg javascript routines
>> not loaded?) or server issue (eg no response on the ajax search queries)
>>
>>
>> dirk
>>
>
> Hi Dirk,
>
> Thanks for the reply. I've checked with a variety of browsers and no
> JavaScript errors are logged to the web console at all.
>
> Strangely, I've noticed I do actually receive search results for some
> queries - but at maximum only four total (where as in the very recent past
> I've had over a dozen for the same search query). I thought perhaps this
> might be a cache memory issue, and reading through the docs I see that it's
> best to have the jspwiki.workDir value explicitly set in jspwiki.properties
> ("The working directory is used to cache things like Lucene search") - I've
> done this and restarted the app server but with no change in behaviour.
>
> Could this behaviour be related to the size of my wiki? It has probably
> several hundred entries at present and in total the content size is 170MB.
> If anything has changed it's been the content uploaded to the wiki, and not
> anything else to my knowledge.
>
>
> Cheers,
> Dave
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz>
>
>
>
> Hi All,
>>>
>>> Yesterday it worked, today it has stopped working. When typing in a
>>> keyword in my JSPWiki search bar, I would usually have dozens of search
>>> hits returned dynamically. This has stopped working altogether, and
>>> nothing
>>> is returned dynamically. I was using JSPWiki 2.8.3, upgrading to 2.9.0
>>> hasn't changed the behaviour (has fixed a couple of other bugs though
>>> which
>>> is lovely). I'm using GlassFish 3.1.2.2 with JDK 6 update 37, all on
>>> OpenIndiana oi_151a7.
>>>
>>> Any pointers to what might have gone wrong here?
>>>
>>> Cheers,
>>> Dave
>>>
>>> --
>>> Dave Koelmeyer
>>> http://blog.davekoelmeyer.co.****nz <http://blog.davekoelmeyer.co.**nz<http://blog.davekoelmeyer.co.nz>
>>> >
>>>
>>>
>>>
>
>
Re: Quick search has stopped working
Posted by Dave Koelmeyer <da...@davekoelmeyer.co.nz>.
On 24/02/13 11:32 AM, Dirk Frederickx wrote:
> Dave,
>
> Can you check the javascript console of the browser ? ( in chrome, Tools
> => Javascript Console)
>
> So you can identify if this is a browser/js issue (eg javascript routines
> not loaded?) or server issue (eg no response on the ajax search queries)
>
>
> dirk
Hi Dirk,
Thanks for the reply. I've checked with a variety of browsers and no
JavaScript errors are logged to the web console at all.
Strangely, I've noticed I do actually receive search results for some
queries - but at maximum only four total (where as in the very recent
past I've had over a dozen for the same search query). I thought perhaps
this might be a cache memory issue, and reading through the docs I see
that it's best to have the jspwiki.workDir value explicitly set in
jspwiki.properties ("The working directory is used to cache things like
Lucene search") - I've done this and restarted the app server but with
no change in behaviour.
Could this behaviour be related to the size of my wiki? It has probably
several hundred entries at present and in total the content size is
170MB. If anything has changed it's been the content uploaded to the
wiki, and not anything else to my knowledge.
Cheers,
Dave
--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz
>> Hi All,
>>
>> Yesterday it worked, today it has stopped working. When typing in a
>> keyword in my JSPWiki search bar, I would usually have dozens of search
>> hits returned dynamically. This has stopped working altogether, and nothing
>> is returned dynamically. I was using JSPWiki 2.8.3, upgrading to 2.9.0
>> hasn't changed the behaviour (has fixed a couple of other bugs though which
>> is lovely). I'm using GlassFish 3.1.2.2 with JDK 6 update 37, all on
>> OpenIndiana oi_151a7.
>>
>> Any pointers to what might have gone wrong here?
>>
>> Cheers,
>> Dave
>>
>> --
>> Dave Koelmeyer
>> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz>
>>
>>
Re: Quick search has stopped working
Posted by Dirk Frederickx <di...@gmail.com>.
Dave,
Can you check the javascript console of the browser ? ( in chrome, Tools
=> Javascript Console)
So you can identify if this is a browser/js issue (eg javascript routines
not loaded?) or server issue (eg no response on the ajax search queries)
dirk
On Sat, Feb 23, 2013 at 12:52 PM, Dave Koelmeyer <
dave.koelmeyer@davekoelmeyer.co.nz> wrote:
> Hi All,
>
> Yesterday it worked, today it has stopped working. When typing in a
> keyword in my JSPWiki search bar, I would usually have dozens of search
> hits returned dynamically. This has stopped working altogether, and nothing
> is returned dynamically. I was using JSPWiki 2.8.3, upgrading to 2.9.0
> hasn't changed the behaviour (has fixed a couple of other bugs though which
> is lovely). I'm using GlassFish 3.1.2.2 with JDK 6 update 37, all on
> OpenIndiana oi_151a7.
>
> Any pointers to what might have gone wrong here?
>
> Cheers,
> Dave
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz>
>
>