You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by "Harry Metske (JIRA)" <ji...@apache.org> on 2013/03/18 21:45:15 UTC
[jira] [Commented] (JSPWIKI-766) Quick Search not working anymore
in Tomcat 7.0.37
[ https://issues.apache.org/jira/browse/JSPWIKI-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605604#comment-13605604 ]
Harry Metske commented on JSPWIKI-766:
--------------------------------------
Hmmm, checking all changes between tomcat 7.0.17 and 7.0.37 is a challenge : http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
Maybe I should just deploy a few tomcat versions, halving the version differences each time, until I find the exact tomcat release that broke things :-) .
> Quick Search not working anymore in Tomcat 7.0.37
> -------------------------------------------------
>
> Key: JSPWIKI-766
> URL: https://issues.apache.org/jira/browse/JSPWIKI-766
> Project: JSPWiki
> Issue Type: Bug
> Components: Core & storage
> Affects Versions: 2.9.1
> Environment: Ubuntu 12.04.1 LTS
> OpenJDK 1.7.0_15
> Tomcat 7.0.37
> JSPWiki JSPWiki v2.9.1-svn-16 and up
> Reporter: Harry Metske
>
> The quicksearch box in the top right corner does not give any search hits anymore.
> A quick analysis with the javascript console reveals that the response is :
> {noformat}
> {"id":10001,"error":{"code":591,"msg":"method not found (session may have timed out)"}}
> {noformat}
> The first test was with JSPWiki version 2.9.1-svn-30.
> To make sure that JSONRPCBridge was not screwed up by the patch for JSPWIKI-659 I deployed JSPWiki v2.9.1-svn-16 and reran the test.
> Still the problem persists.
> I remembered I recently upgraded tomcat to the latest release 7.0.37, so I decided to backout to my previous tomcat version (7.0.17).
> And guess what, quicksearch works again.
> I will dig into the tomcat changelog to see if I can find a possible cause.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira