Details

    • Type: Documentation
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Attachments:
      6
    • Comments:
      12
    • Documentation Status:
      Needed

      Description

      When using Tomcat 7.0.29, heap space shoots up to over 600MB when starting up DSpace, only deploying the XMLUI exploded war. Even without SOLR.

      Using Tomcat 7.0.40, this is no longer the case and just uses 50MB of heap.

      Right now, I'm not sure whether this is just a local configuration problem, or whether there's a serious reason to put a warning in the docs to ensure that people don't use 7.0.29.

      Would be great if anybody is able to reproduce/confirm this excessive memory usage on tomcat 7.0.29.

      Java opts for 7.0.29 -Xms1024m -Xmx1024m (won't even run without declaring more heap space).

        Attachments

        1. 7.0.29-classes.png
          7.0.29-classes.png
          180 kB
        2. 7.0.29-telemetry.png
          7.0.29-telemetry.png
          27 kB
        3. 7.0.40-classes.png
          7.0.40-classes.png
          171 kB
        4. 7.0.40-telemetry.png
          7.0.40-telemetry.png
          56 kB
        5. PSI-Probe-Tomcat-7.0.30.png
          PSI-Probe-Tomcat-7.0.30.png
          119 kB
        6. PSI-Probe-Tomcat-7.0.40.png
          PSI-Probe-Tomcat-7.0.40.png
          129 kB

          Activity

            People

            • Assignee:
              bram Bram Luyten (Atmire)
              Reporter:
              bram Bram Luyten (Atmire)
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: