Uploaded image for project: 'Continuum'
  1. Continuum
  2. CONTINUUM-1353

after a few weeks, continuum runs into outofmemory error

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 1.1-alpha-2
    • 1.1-beta-3
    • Core system
    • None

    Description

      when clicking on the build history, memory of the jvm increases from 100MB until 470MB
      after that it crashes with outofmemory error (JDO exception)
      Increasing the plexus jvm memory does have no affect:
      %PLEXUS_JAVA_EXE% %PLEXUS_OPTS% -Xmx900M -XX:MaxPermSize=128m -classpath "%PLEXUS_HOME%\core\boot\plexus-classworlds-1.2-alpha-7.jar" -Dclassworlds.conf="%PLEXUS_HOME%\conf\classworlds.conf" -Dplexus.core=%PLEXUS_CORE% -Dplexus.system.path="%PATH%" -Djava.io.tmpdir=%PLEXUS_TMPDIR% -Dplexus.home="%PLEXUS_HOME%" -Dappserver.base="%PLEXUS_BASE%" -Dtools.jar="%TOOLS_JAR%" org.codehaus.plexus.classworlds.launcher.Launcher %PLEXUS_CMD_LINE_ARGS%

      So probably bug in fetch from db where all objects are retrieved ?
      For us this is a showstopper. Would MySQL DB be a workaround ? I guess the query is the same, so will the memory usage be ?

      Where can I find the complete DDL script for mysql ? On the wiki there is only 1 table ... ?

      javax.jdo.JDODataStoreException: Iteration request failed :
      SELECT THIS.CHANGEFILE_ID,THIS.MODEL_ENCODING,THIS."NAME",THIS.REVISION,THIS.STATUS,THIS.FILES_INTEGER_IDX AS JPOXORDER0 FROM
      CHANGEFILE THIS WHERE ? = THIS.FILES_CHANGESET_ID_OID AND THIS.FILES_INTEGER_IDX >= ? ORDER BY JPOXORDER0 NestedThrowables: SQL Exception: Java exception:
      'Java heap space: java.lang.OutOfMemoryError'.

      Attachments

        Activity

          People

            Unassigned Unassigned
            tony.nys@inglease.be tony nys
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: