[jira] Closed: (JCR-386) Query dump failed with deep query tree

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/JCR-386?page=all ]
     
Marcel Reutegger closed JCR-386:
--------------------------------


Thanks for reporting this issue.

> Query dump failed with deep query tree
> --------------------------------------
>
>          Key: JCR-386
>          URL: http://issues.apache.org/jira/browse/JCR-386
>      Project: Jackrabbit
>         Type: Bug

>   Components: query
>     Versions: 1.0
>  Environment: Jackrabbit 1.0 RC3
>     Reporter: Raphael Franchet
>     Assignee: Marcel Reutegger
>     Priority: Minor
>      Fix For: 1.0.1

>
> With a big query (more than 400 OR operands) the query dump failed.
> The query dump is made at QueryImpl.execute (line 136)
> It failed because of the constant PADDING at QueryTreeDump.visit(line 85).
> The constant PADDING is a 255 character array, but in my program it would need it to be bigger.
> I think putting it to 65535 would not be a problem : it would only take a little bit more memory.
> This is the top of the stacktract for info:
> java.lang.ArrayIndexOutOfBoundsException
> 	at java.lang.System.arraycopy(Native Method)
> 	at java.lang.StringBuffer.append(StringBuffer.java:499)
> 	at org.apache.jackrabbit.core.query.QueryTreeDump.visit(QueryTreeDump.java:85)
> 	at org.apache.jackrabbit.core.query.OrQueryNode.accept(OrQueryNode.java:50)
> 	at org.apache.jackrabbit.core.query.QueryTreeDump.traverse(QueryTreeDump.java:263)
>                      ...
> This is not critical because I can avoid the dump by unactivating debug logs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira