Maven 2.x Changes Plugin

Setting maxEntries too high causes a SAXParseException

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta-2
  • Fix Version/s: 2.0
  • Component/s: jira
  • Labels:
    None
  • Environment:
    maven 2.0.6
  • Number of attachments :
    0

Description

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
John Casey added a comment -

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)

Show
John Casey added a comment - 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 )
Hide
Permalink
Dennis Lundberg added a comment -

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

mvn site -DentityExpansionLimit=100000

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.

Show
Dennis Lundberg added a comment - 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 mvn site -DentityExpansionLimit=100000 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.
Hide
Permalink
Dennis Lundberg added a comment -

I have documented a work-around in the FAQ.

Show
Dennis Lundberg added a comment - I have documented a work-around in the FAQ.

People

  • Assignee:
    Dennis Lundberg
    Reporter:
    John Casey
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: