Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.6
    • Fix Version/s: 0.6
    • Component/s: Core operations
    • Labels:
      None

      Description

      If there is a sitemap.xmap file in the "project.content-dir", the build process of a site (target: "site") will hang with an OutOfMemoryError.

        Issue Links

          Activity

          Hide
          David Crossley added a comment -
          It is already fixed. The procedure that you followed was for the old project sitemap method. Sorry the README.txt confused you, now fixed.
          http://forrest.apache.org/docs/upgrading_06.html
          http://forrest.apache.org/docs/project-sitemap.html
          Show
          David Crossley added a comment - It is already fixed. The procedure that you followed was for the old project sitemap method. Sorry the README.txt confused you, now fixed. http://forrest.apache.org/docs/upgrading_06.html http://forrest.apache.org/docs/project-sitemap.html
          Hide
          Lorenz Froihofer added a comment -
          I cannot verify that this bug is resolved.
          The following:
          1.) create a new directory, change to this directory
          2.) execute "forrest seed"
          3.) copy sitemap.xmap from "$FORREST_HOME/context" to src/documentation
          4.) execute "forrest site"

          still causes a java.lang.OutOfMemoryException.

          If these steps are no longer appropriate, src/documentation/README.txt (of the fresh site) has to be updated to reflect the new procedure.
          Show
          Lorenz Froihofer added a comment - I cannot verify that this bug is resolved. The following: 1.) create a new directory, change to this directory 2.) execute "forrest seed" 3.) copy sitemap.xmap from "$FORREST_HOME/context" to src/documentation 4.) execute "forrest site" still causes a java.lang.OutOfMemoryException. If these steps are no longer appropriate, src/documentation/README.txt (of the fresh site) has to be updated to reflect the new procedure.
          Hide
          Nicola Ken Barozzi added a comment -
          Ok, this works now with the new sitemap extension system.
          Show
          Nicola Ken Barozzi added a comment - Ok, this works now with the new sitemap extension system.
          Hide
          Nicola Ken Barozzi added a comment -
          This is a by product of currently unfinished copyless.
          The solution is not to make the user sitemap override the forrest ones, but to be an indipendent sitemap mounted in it's own internal path space.

          Forrest should then be instructed to go and search for source files also there, thus making it into a preprocessing sitemap.
          Show
          Nicola Ken Barozzi added a comment - This is a by product of currently unfinished copyless. The solution is not to make the user sitemap override the forrest ones, but to be an indipendent sitemap mounted in it's own internal path space. Forrest should then be instructed to go and search for source files also there, thus making it into a preprocessing sitemap.
          Hide
          Dave Brondsema added a comment -
          In cocoon.xconf, <sitemap> specifies file="context://sitemap.xmap". And that context: URI is specified later in a source-factories/component-instance

          I think it'd be good to make cocoon.xconf directly mount the project sitemap and not load the forrest sitemap at all. Perhaps create a source-factories/component-instance that would check the project dir and use the file if it was there and if not, it would use the corresponding forrest file?
          Show
          Dave Brondsema added a comment - In cocoon.xconf, <sitemap> specifies file=" context://sitemap.xmap ". And that context: URI is specified later in a source-factories/component-instance I think it'd be good to make cocoon.xconf directly mount the project sitemap and not load the forrest sitemap at all. Perhaps create a source-factories/component-instance that would check the project dir and use the file if it was there and if not, it would use the corresponding forrest file?
          Hide
          Thorsten Scherler added a comment -
          Gregor wrote in the lenya dev-ml about a similar task: "it could also be a compile-time option. ant has a xslt task that could accomplish this."

          We had to put that in the ant target (forrest / forrest run) and just comment out the section in the ${project_home}-sitemap.xmap (if its still in there). In the long run we have to solve the problem in a higher level (but I do not have an idea for that).
          Show
          Thorsten Scherler added a comment - Gregor wrote in the lenya dev-ml about a similar task: "it could also be a compile-time option. ant has a xslt task that could accomplish this." We had to put that in the ant target (forrest / forrest run) and just comment out the section in the ${project_home}-sitemap.xmap (if its still in there). In the long run we have to solve the problem in a higher level (but I do not have an idea for that).
          Hide
          Thorsten Scherler added a comment -
          Happends also with a /forrest run/ not only with /forrest/.
          Show
          Thorsten Scherler added a comment - Happends also with a /forrest run/ not only with /forrest/.
          Hide
          Dave Brondsema added a comment -
          The following pipeline needs to be removed manually from the project sitemap.xmap. Or find some way to not select this when it is in the project sitemap already. I have no idea how do to this, though. Is there some way we can get the current filename and see if it is the same as {project:sitemap}?

                <map:pipeline internal-only="false">
                <map:select type="exists">
                  <map:when test="{project:sitemap}">
                    <map:mount uri-prefix="" src="{project:sitemap}" check-reload="yes" />
                  </map:when>
                </map:select>
                </map:pipeline>
          Show
          Dave Brondsema added a comment - The following pipeline needs to be removed manually from the project sitemap.xmap. Or find some way to not select this when it is in the project sitemap already. I have no idea how do to this, though. Is there some way we can get the current filename and see if it is the same as {project:sitemap}?       <map:pipeline internal-only="false">       <map:select type="exists">         <map:when test="{project:sitemap}">           <map:mount uri-prefix="" src="{project:sitemap}" check-reload="yes" />         </map:when>       </map:select>       </map:pipeline>
          Hide
          David Crossley added a comment -
          Show
          David Crossley added a comment - This issue is also described at: http://marc.theaimsgroup.com/?l=forrest-dev&m=108797686824095
          Hide
          David Crossley added a comment -
          After waiting some time, the following occurs:

          Logging Error: Unknown error writing event.
          java.lang.OutOfMemoryError
          * [1/0] [0/0] 94.501s 0b index.html
          Exception in thread "main" java.lang.OutOfMemoryError

          To reproduce this error:
          ========================
          1.) create a new directory, change to this directory
          2.) execute "forrest seed"
          3.) copy sitemap.xmap from "$FORREST_HOME/context" to src/documentation
          4.) execute "forrest site"

          (Snipped build output as it does not add value.)
          Show
          David Crossley added a comment - After waiting some time, the following occurs: Logging Error: Unknown error writing event. java.lang.OutOfMemoryError * [1/0] [0/0] 94.501s 0b index.html Exception in thread "main" java.lang.OutOfMemoryError To reproduce this error: ======================== 1.) create a new directory, change to this directory 2.) execute "forrest seed" 3.) copy sitemap.xmap from "$FORREST_HOME/context" to src/documentation 4.) execute "forrest site" (Snipped build output as it does not add value.)

            People

            • Assignee:
              Nicola Ken Barozzi
              Reporter:
              Lorenz Froihofer
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development