You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Raphael Franchet (JIRA)" <ji...@apache.org> on 2006/04/04 16:44:47 UTC
[jira] Created: (JCR-386) Query dump failed with deep query tree
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
Priority: Minor
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
[jira] Closed: (JCR-386) Query dump failed with deep query tree
Posted by "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
[jira] Assigned: (JCR-386) Query dump failed with deep query tree
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-386?page=all ]
Marcel Reutegger reassigned JCR-386:
------------------------------------
Assign To: Marcel Reutegger
> 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
>
> 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
[jira] Resolved: (JCR-386) Query dump failed with deep query tree
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-386?page=all ]
Marcel Reutegger resolved JCR-386:
----------------------------------
Fix Version: 1.0.1
Resolution: Fixed
The padding array now grows when more characters are needed.
Fixed in revision: 391564
> 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
[jira] Commented: (JCR-386) Query dump failed with deep query tree
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-386?page=comments#action_12413334 ]
Jukka Zitting commented on JCR-386:
-----------------------------------
Merged for 1.0.1 in revision 409538.
> 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