[ 
https://issues.apache.org/jira/browse/JSPWIKI-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333224#comment-14333224
 ] 

David Vittor commented on JSPWIKI-566:
--------------------------------------

Hmm seems to still be the same error:

Somehow the search is calling Search.jsp -> ViewTemplate.jsp -> FindContent.jsp 
-> AjaxSearch.jsp - and somehow this ends us in an infinite regex pattern. 

I think the error is somehow in the SearchManager.java or the 
LuceneSearchProvider.java findPages() method, but will need to debug this to 
see.

{noformat}
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615)
        at java.util.regex.Pattern$BranchConn.match(Pattern.java:4466)
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3694)
        at java.util.regex.Pattern$Branch.match(Pattern.java:4502)
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
        at java.util.regex.Pattern$LazyLoop.match(Pattern.java:4745)
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615)
        at java.util.regex.Pattern$BranchConn.match(Pattern.java:4466)
2015-02-13 21:27:50,124 [http-nio-9180-exec-1] ERROR 
org.apache.wiki.tags.WikiTagBase JSPWiki:/JSPWiki/Search.jsp 
JSPWiki:http://digitalspider.com.au/JSPWiki/Search.jsp - 
javax.servlet.ServletException: java.lang.StackOverflowError
javax.servlet.jsp.JspException: javax.servlet.ServletException: 
java.lang.StackOverflowError
        at org.apache.wiki.tags.IncludeTag.doEndTag(IncludeTag.java:91)
        at 
org.apache.jsp.templates.default_.FindContent_jsp._jspx_meth_wiki_005fInclude_005f0(FindContent_jsp.java:833)
        at 
org.apache.jsp.templates.default_.FindContent_jsp._jspService(FindContent_jsp.java:254)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
        at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
        at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:405)
{noformat}

This error result in the jspwiki-commons.jsp coming back with some result value 
(the error), but result.each does not exist!
{noformat}
           Wiki.ajaxJsonCall("/search/pages",[qv,'20'], function(result) {
                        $('searchSpin').hide();
                        if(!result) return;
                        var frag = new Element('ul');

                        result.each(function(el){
                                new Element('li').adopt(
                                        new 
Element('a',{'href':Wiki.getUrl(el.page) }).setHTML(el.page),
                                        new 
Element('span',{'class':'small'}).setHTML(" ("+el.score+")")
                                ).inject(frag);
                        });
                        $('searchOutput').empty().adopt(frag);
                        Wiki.locatemenu( $('query'), $('searchboxMenu') );
           });
{noformat}

> AJAX server-side rewrite
> ------------------------
>
>                 Key: JSPWIKI-566
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-566
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Core & storage
>    Affects Versions: 2.10.1
>            Reporter: Janne Jalkanen
>            Assignee: David Vittor
>             Fix For: 2.10.2
>
>         Attachments: JSPWIKI-566.png, ajaxDispatchServlet.patch, 
> ajaxFunctions.patch, ajaxFunctions.patch, ajaxFunctions.patch, 
> ajaxFunctions.patch, ajaxFunctions.patch, test.html
>
>
> The AJAX library we're currently using is a bit problematic, as it stores 
> non-serializable stuff in the HttpSession (causing all sorts of nasty 
> exception reports in default configurations of Tomcat, and preventing 
> clustering).  It does provide a very nice, reflection-based interface so that 
> we can expose any class/method as a JSON endpoint, but this does not really 
> work well with our auth system.
> We should replace the jabsorb stuff with a Stripes-native solution (possibly 
> with some extensions to allow particular beans to expose methods as if we 
> were using jabsorb).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to