You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2007/04/11 02:06:46 UTC
[jira] Created: (MCHANGES-75) Setting maxEntries results in
incorrect JIRA results
Setting maxEntries results in incorrect JIRA results
----------------------------------------------------
Key: MCHANGES-75
URL: http://jira.codehaus.org/browse/MCHANGES-75
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-2
Environment: maven 2.0.6
Reporter: John Casey
When I configure maxEntries == 500 and point the jira-report at http://jira.codehaus.org/browse/MNG, it fails to parse the resulting XML, saying it has exceeded 64,000 entity expansions (something to do with SAX). The error is:
org.xml.sax.SAXParseException: Parser has reached the entity expansion limit "64,000" set by the Application.
When I wget the URL that the changes plugin has generated:
http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10500&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=500&reset=true&decorator=none
it shows results from XWIRE and XULUX...clearly not limited to MNG.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-75) Setting maxEntries results in
incorrect JIRA results
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101607 ]
Dennis Lundberg commented on MCHANGES-75:
-----------------------------------------
This seems to be a limit in the SAX parser. The error happens when there are a lot of entities like & and such in the file being parsed. I got around this one by specifying an explicit value for this limit on the command line
{code}
mvn site -DentityExpansionLimit=100000
{code}
When doing that, I *only* got issues for MNG - not any other project. So that may have been a glitch in codehaus JIRA at that time.
However, I have not been successful in doing this programatically in the plugin. You can set properties on the parser, but I don't know the correct id for the property.
> Setting maxEntries results in incorrect JIRA results
> ----------------------------------------------------
>
> Key: MCHANGES-75
> URL: http://jira.codehaus.org/browse/MCHANGES-75
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira-report
> Affects Versions: 2.0-beta-2
> Environment: maven 2.0.6
> Reporter: John Casey
>
> When I configure maxEntries == 500 and point the jira-report at http://jira.codehaus.org/browse/MNG, it fails to parse the resulting XML, saying it has exceeded 64,000 entity expansions (something to do with SAX). The error is:
> org.xml.sax.SAXParseException: Parser has reached the entity expansion limit "64,000" set by the Application.
> When I wget the URL that the changes plugin has generated:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10500&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=500&reset=true&decorator=none
> it shows results from XWIRE and XULUX...clearly not limited to MNG.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGES-75) Setting maxEntries results in
incorrect JIRA results
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MCHANGES-75:
------------------------------------
Component/s: jira-report
> Setting maxEntries results in incorrect JIRA results
> ----------------------------------------------------
>
> Key: MCHANGES-75
> URL: http://jira.codehaus.org/browse/MCHANGES-75
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira-report
> Affects Versions: 2.0-beta-2
> Environment: maven 2.0.6
> Reporter: John Casey
>
> When I configure maxEntries == 500 and point the jira-report at http://jira.codehaus.org/browse/MNG, it fails to parse the resulting XML, saying it has exceeded 64,000 entity expansions (something to do with SAX). The error is:
> org.xml.sax.SAXParseException: Parser has reached the entity expansion limit "64,000" set by the Application.
> When I wget the URL that the changes plugin has generated:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10500&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=500&reset=true&decorator=none
> it shows results from XWIRE and XULUX...clearly not limited to MNG.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGES-75) Setting maxEntries too high causes a
SAXParseException
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MCHANGES-75:
------------------------------------
Summary: Setting maxEntries too high causes a SAXParseException (was: Setting maxEntries results in incorrect JIRA results)
> Setting maxEntries too high causes a SAXParseException
> ------------------------------------------------------
>
> Key: MCHANGES-75
> URL: http://jira.codehaus.org/browse/MCHANGES-75
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira-report
> Affects Versions: 2.0-beta-2
> Environment: maven 2.0.6
> Reporter: John Casey
>
> When I configure maxEntries == 500 and point the jira-report at http://jira.codehaus.org/browse/MNG, it fails to parse the resulting XML, saying it has exceeded 64,000 entity expansions (something to do with SAX). The error is:
> org.xml.sax.SAXParseException: Parser has reached the entity expansion limit "64,000" set by the Application.
> When I wget the URL that the changes plugin has generated:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10500&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=500&reset=true&decorator=none
> it shows results from XWIRE and XULUX...clearly not limited to MNG.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-75) Setting maxEntries results in
incorrect JIRA results
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92519 ]
John Casey commented on MCHANGES-75:
------------------------------------
The same thing happens if I use the issueManagement URL:
http://jira.codehaus.org/secure/BrowseProject.jspa?pid=10500
(I had been using http://jira.codehaus.org/browse/MNG)
> Setting maxEntries results in incorrect JIRA results
> ----------------------------------------------------
>
> Key: MCHANGES-75
> URL: http://jira.codehaus.org/browse/MCHANGES-75
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-2
> Environment: maven 2.0.6
> Reporter: John Casey
>
> When I configure maxEntries == 500 and point the jira-report at http://jira.codehaus.org/browse/MNG, it fails to parse the resulting XML, saying it has exceeded 64,000 entity expansions (something to do with SAX). The error is:
> org.xml.sax.SAXParseException: Parser has reached the entity expansion limit "64,000" set by the Application.
> When I wget the URL that the changes plugin has generated:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10500&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=500&reset=true&decorator=none
> it shows results from XWIRE and XULUX...clearly not limited to MNG.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCHANGES-75) Setting maxEntries too high causes a
SAXParseException
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MCHANGES-75.
-----------------------------------
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: 2.0-beta-4
I have documented a work-around in the FAQ.
> Setting maxEntries too high causes a SAXParseException
> ------------------------------------------------------
>
> Key: MCHANGES-75
> URL: http://jira.codehaus.org/browse/MCHANGES-75
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira-report
> Affects Versions: 2.0-beta-2
> Environment: maven 2.0.6
> Reporter: John Casey
> Assignee: Dennis Lundberg
> Fix For: 2.0-beta-4
>
>
> When I configure maxEntries == 500 and point the jira-report at http://jira.codehaus.org/browse/MNG, it fails to parse the resulting XML, saying it has exceeded 64,000 entity expansions (something to do with SAX). The error is:
> org.xml.sax.SAXParseException: Parser has reached the entity expansion limit "64,000" set by the Application.
> When I wget the URL that the changes plugin has generated:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10500&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=500&reset=true&decorator=none
> it shows results from XWIRE and XULUX...clearly not limited to MNG.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira