You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "tony nys (JIRA)" <ji...@codehaus.org> on 2007/07/25 08:38:13 UTC
[jira] Created: (CONTINUUM-1353) after a few weeks, continuum runs
into outofmemory error
after a few weeks, continuum runs into outofmemory error
--------------------------------------------------------
Key: CONTINUUM-1353
URL: http://jira.codehaus.org/browse/CONTINUUM-1353
Project: Continuum
Issue Type: Bug
Components: Core system
Affects Versions: 1.1-alpha-2
Reporter: tony nys
Priority: Blocker
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'.
--
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: (CONTINUUM-1353) after a few weeks, continuum
runs into outofmemory error
Posted by "tony nys (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103747 ]
tony nys commented on CONTINUUM-1353:
-------------------------------------
367612 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Changes found, building
367612 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action update-project-from-working-directory
367612 [pool-1-thread-1] INFO org.codehaus.plexus.action.Action:update-project-from-working-directory - Updating project 'WPM Solutions - Financial/Lending - Lease Service Implementation' from checkout.
367768 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action execute-builder
367972 [pool-1-thread-1] INFO org.apache.maven.continuum.utils.shell.ShellCommandHelper:default - Executing: C:\apps\maven-2.0.7\bin\mvn --batch-mode --non-recursive -Dmaven.test.skip=true clean deploy
367972 [pool-1-thread-1] INFO org.apache.maven.continuum.utils.shell.ShellCommandHelper:default - Working directory: C:\apps\continuum-data\working-directory\11
377456 [pool-1-thread-1] INFO org.apache.maven.continuum.execution.ContinuumBuildExecutor:maven2 - Exit code: 0
377675 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action deploy-artifact
377722 [pool-1-thread-1] INFO org.apache.maven.artifact.repository.metadata.RepositoryMetadataManager:default - Retrieving previous metadata from deployment-repository
377753 [pool-1-thread-1] INFO org.apache.maven.artifact.manager.WagonManager:default - Uploading project information for solutions-fl-lease-service-implementation 2.1.0
377768 [pool-1-thread-1] INFO org.apache.maven.artifact.repository.metadata.RepositoryMetadataManager:default - Retrieving previous metadata from deployment-repository
377768 [pool-1-thread-1] INFO org.apache.maven.artifact.manager.WagonManager:default - Uploading repository metadata for: 'artifact com.accelior.wpm:solutions-fl-lease-service-implementation'
377956 [pool-1-thread-1] INFO org.codehaus.plexus.notification.notifier.Notifier:mail - Same state, not sending message.
377956 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Initializing build
582504 [Thread-6] ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - Error executing task
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Java heap space
at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299)
at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:128)
at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:165)
at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:127)
Caused by: java.lang.OutOfMemoryError: Java heap space
582504 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Initializing build
582535 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Starting build of Web Enabled Leasing Model
582582 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Purging exiting working copy
582582 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action clean-working-directory
584035 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Updating working dir
584035 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action check-working-directory
584035 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action checkout-project
584035 [pool-1-thread-1] INFO org.apache.maven.continuum.scm.ContinuumScm:default - Checking out project: 'Web Enabled Leasing Model', id: '18' to 'C:\apps\continuum-data\working-directory\18'.
584035 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Executing: cvs -z3 -f -d :pserver:tony.nys@sloc18:/ACCELIOR_LOCAL -q checkout -d 18 ING-LEASE/WEL-302/wel-model
584035 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Working directory: C:\apps\continuum-data\working-directory
584895 [pool-1-thread-1] INFO org.apache.maven.continuum.scm.ContinuumScm:default - Checked out 12 files.
584895 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Merging SCM results
584957 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Changes found, building
584957 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action update-project-from-working-directory
584973 [pool-1-thread-1] INFO org.codehaus.plexus.action.Action:update-project-from-working-directory - Updating project 'Web Enabled Leasing Model' from checkout.
585098 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action execute-builder
585239 [pool-1-thread-1] INFO org.apache.maven.continuum.utils.shell.ShellCommandHelper:default - Executing: C:\apps\maven-2.0.7\bin\mvn --batch-mode --non-recursive -Dmaven.test.skip=true clean deploy
> after a few weeks, continuum runs into outofmemory error
> --------------------------------------------------------
>
> Key: CONTINUUM-1353
> URL: http://jira.codehaus.org/browse/CONTINUUM-1353
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Affects Versions: 1.1-alpha-2
> Reporter: tony nys
> Priority: Blocker
>
> 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'.
--
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: (CONTINUUM-1353) after a few weeks, continuum
runs into outofmemory error
Posted by "tony nys (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103746 ]
tony nys commented on CONTINUUM-1353:
-------------------------------------
ij> select count(*) from changefile;
1
-----------
3809325
select count(*) from changeset;
1
-----------
16146
> after a few weeks, continuum runs into outofmemory error
> --------------------------------------------------------
>
> Key: CONTINUUM-1353
> URL: http://jira.codehaus.org/browse/CONTINUUM-1353
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Affects Versions: 1.1-alpha-2
> Reporter: tony nys
> Priority: Blocker
>
> 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'.
--
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: (CONTINUUM-1353) after a few weeks, continuum
runs into outofmemory error
Posted by "tony nys (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103750 ]
tony nys commented on CONTINUUM-1353:
-------------------------------------
deleting records from these tables fixes the problem temporarily...
BUILDRESULT
BUILDRESULT_MODIFIEDDEPENDENCIES
CHANGEFILE
CHANGESET
> after a few weeks, continuum runs into outofmemory error
> --------------------------------------------------------
>
> Key: CONTINUUM-1353
> URL: http://jira.codehaus.org/browse/CONTINUUM-1353
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Affects Versions: 1.1-alpha-2
> Reporter: tony nys
> Priority: Blocker
>
> 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'.
--
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: (CONTINUUM-1353) after a few weeks, continuum
runs into outofmemory error
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107740 ]
Emmanuel Venisse commented on CONTINUUM-1353:
---------------------------------------------
The "build fresh" option do a clean checkout for each build.
In 1.1-beta-3, we fixed it and add a new option to run always a build definition even with no modification with an update.
When you'll test beta-3, let us know if you have always this OOME, so we'll can close this issue
> after a few weeks, continuum runs into outofmemory error
> --------------------------------------------------------
>
> Key: CONTINUUM-1353
> URL: http://jira.codehaus.org/browse/CONTINUUM-1353
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Affects Versions: 1.1-alpha-2
> Reporter: tony nys
> Priority: Blocker
>
> 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'.
--
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: (CONTINUUM-1353) after a few weeks, continuum
runs into outofmemory error
Posted by "tony nys (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105290 ]
tony nys commented on CONTINUUM-1353:
-------------------------------------
When will this issue be fixed ?
It is really annoying: every 2 weeks, I need to clean up the database manually and bring continuum offline
> after a few weeks, continuum runs into outofmemory error
> --------------------------------------------------------
>
> Key: CONTINUUM-1353
> URL: http://jira.codehaus.org/browse/CONTINUUM-1353
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Affects Versions: 1.1-alpha-2
> Reporter: tony nys
> Priority: Blocker
>
> 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'.
--
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: (CONTINUUM-1353) after a few weeks, continuum
runs into outofmemory error
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107731 ]
Emmanuel Venisse commented on CONTINUUM-1353:
---------------------------------------------
Do you use the build fresh option? Before 1.1-beta-3, we have an memory issue with it that is fixed.
> after a few weeks, continuum runs into outofmemory error
> --------------------------------------------------------
>
> Key: CONTINUUM-1353
> URL: http://jira.codehaus.org/browse/CONTINUUM-1353
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Affects Versions: 1.1-alpha-2
> Reporter: tony nys
> Priority: Blocker
>
> 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'.
--
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: (CONTINUUM-1353) after a few weeks, continuum
runs into outofmemory error
Posted by "tony nys (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107733 ]
tony nys commented on CONTINUUM-1353:
-------------------------------------
using refresh option & continuum-1.1-alpha-2
what does the refresh option actually do ? a complete fresh cvs checkout ?
> after a few weeks, continuum runs into outofmemory error
> --------------------------------------------------------
>
> Key: CONTINUUM-1353
> URL: http://jira.codehaus.org/browse/CONTINUUM-1353
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Affects Versions: 1.1-alpha-2
> Reporter: tony nys
> Priority: Blocker
>
> 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'.
--
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: (CONTINUUM-1353) after a few weeks, continuum
runs into outofmemory error
Posted by "tony nys (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103743 ]
tony nys commented on CONTINUUM-1353:
-------------------------------------
really showstopper, apparently not only happens in webinterface, also at runtime,
continuum queries db and.. bang !
> after a few weeks, continuum runs into outofmemory error
> --------------------------------------------------------
>
> Key: CONTINUUM-1353
> URL: http://jira.codehaus.org/browse/CONTINUUM-1353
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Affects Versions: 1.1-alpha-2
> Reporter: tony nys
> Priority: Blocker
>
> 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'.
--
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: (CONTINUUM-1353) after a few weeks, continuum
runs into outofmemory error
Posted by "tony nys (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103181 ]
tony nys commented on CONTINUUM-1353:
-------------------------------------
Error really occurs clicking on a build result on the build history page
now changed memory param in wrapper.conf (not in plexus.bat) to 900M
Mem increases now from 120MB until 930MB then crashes
jvm 1 | java.lang.ArrayStoreException
jvm 1 | at java.util.ArrayList.add(ArrayList.java:352)
jvm 1 | at org.jpox.util.ReferenceValueMap.values(ReferenceValueMap.java:314)
jvm 1 | at org.jpox.cache.WeakRefCache.values(WeakRefCache.java:125)
jvm 1 | at org.jpox.AbstractPersistenceManager.disconnectSMCache(AbstractPersistenceManager.java:616)
jvm 1 | at org.jpox.AbstractPersistenceManager.close(AbstractPersistenceManager.java:598)
jvm 1 | at org.codehaus.plexus.jdo.PlexusJdoUtils.closePersistenceManager(PlexusJdoUtils.java:427)
jvm 1 | at org.codehaus.plexus.jdo.PlexusJdoUtils.rollbackIfActive(PlexusJdoUtils.java:419)
jvm 1 | at org.apache.maven.continuum.store.JdoContinuumStore.rollback(JdoContinuumStore.java:745)
jvm 1 | at org.apache.maven.continuum.store.JdoContinuumStore.getBuildResultsForProject(JdoContinuumSt
ore.java:1071)
jvm 1 | at org.apache.maven.continuum.DefaultContinuum.getChangesSinceLastSuccess(DefaultContinuum.jav
a:1020)
jvm 1 | at org.apache.maven.continuum.web.action.BuildResultAction.execute(BuildResultAction.java:81)
jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
jvm 1 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
jvm 1 | at java.lang.reflect.Method.invoke(Method.java:585)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:36
4)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.jav
a:216)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
jvm 1 | at com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowIn
terceptor.java:168)
jvm 1 | at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterIntercepto
r.java:86)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.ja
va:115)
jvm 1 | at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterIntercepto
r.java:86)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at org.apache.maven.continuum.web.interceptor.ForceContinuumConfigurationInterceptor.intercept
(ForceContinuumConfigurationInterceptor.java:73)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(Policy
EnforcementInterceptor.java:103)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActio
nInterceptor.java:178)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at org.codehaus.plexus.xwork.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappin
gInterceptor.java:58)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowIn
terceptor.java:168)
jvm 1 | at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterIntercepto
r.java:86)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.ja
va:115)
jvm 1 | at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterIntercepto
r.java:86)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.webwork.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.
java:171)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.webwork.interceptor.debugging.DebuggingInterceptor.intercept(DebuggingInte
rceptor.java:147)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.interceptor.I18nInterceptor.intercept(I18nInterceptor.java:151)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingIn
terceptor.java:186)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at org.codehaus.plexus.redback.xwork.interceptor.AutoLoginInterceptor.intercept(AutoLoginInter
ceptor.java:156)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at org.codehaus.plexus.redback.xwork.interceptor.ForceAdminUserInterceptor.intercept(ForceAdmi
nUserInterceptor.java:63)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at org.codehaus.plexus.redback.xwork.interceptor.EnvironmentCheckInterceptor.intercept(Environ
mentCheckInterceptor.java:122)
jvm 1 | at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
jvm 1 | at com.opensymphony.xwork.DefaultActionProxy.execute(DefaultActionProxy.java:113)
jvm 1 | at com.opensymphony.webwork.dispatcher.DispatcherUtils.serviceAction(DispatcherUtils.java:225)
jvm 1 | at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:202)
jvm 1 | at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.
java:821)
jvm 1 | at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
jvm 1 | at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
jvm 1 | at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.
java:821)
jvm 1 | at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java
:88)
jvm 1 | at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.
java:821)
jvm 1 | at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
jvm 1 | at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
jvm 1 | at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
jvm 1 | at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
jvm 1 | at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
jvm 1 | at org.mortbay.http.HttpServer.service(HttpServer.java:909)
jvm 1 | at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
jvm 1 | at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
jvm 1 | at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
jvm 1 | at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
jvm 1 | at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
jvm 1 | at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
> after a few weeks, continuum runs into outofmemory error
> --------------------------------------------------------
>
> Key: CONTINUUM-1353
> URL: http://jira.codehaus.org/browse/CONTINUUM-1353
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Affects Versions: 1.1-alpha-2
> Reporter: tony nys
> Priority: Blocker
>
> 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'.
--
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