Your browser was unable to load all of the resources. They may
have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.
./console.log:jvm 1 | Caused by: com.pmease.quickbuild.plugin.report.engine.exception.DatabaseException: Failed executing update sql [INSERT INTO tests_trends(packagename, classname, testname, runs, failures, skips, averageduration, lastrunbuild, currentstatus, latestbuilds, lateststatuses, latestdurations) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)] on database /storage/quickbuild-data/configurations/246/reports/junit/XUnit/junit.h2.db
./console.log:jvm 1 | Caused by: java.sql.SQLException: Out of memory.; SQL statement:
./quickbuild.log.2: Caused by: com.pmease.quickbuild.plugin.report.engine.exception.DatabaseException: Failed executing update sql [INSERT INTO tests_trends(packagename, classname, testname, runs, failures, skips, averageduration, lastrunbuild, currentstatus, latestbuilds, lateststatuses, latestdurations) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)] on database /storage/quickbuild-data/configurations/246/reports/junit/XUnit/junit.h2.db
./quickbuild.log.2: Caused by: java.sql.SQLException: Out of memory.; SQL statement:
i have MaxPermSize=512m, wrapper.java.initmemory=2048 and wrapper.java.maxmemory=8192 already. any idea what is causing this?
-
replies
8
-
views
3169
-
stars
0
-
btw, there are still 8G of free memory on the server, plenty for mysql
This is not caused by MySQL, QuickBuild use h2 as report database. So please check whether your QuickBuild is out of memory.
You can increase QuickBuild memory by editing line below in file ${quickbuild-home}/conf/wrapper.conf
wrapper.java.maxmemory = BIGGER_SIZE
i have wrapper.java.maxmemory=8192 already. is 8GB not enough?
It all depends on your server load. You can check your server information by visiting page: http://your-server-url/sever_info
Normally, 8G should be enough if server is mainly for scheduling build and web visiting.
Please also check below file and tell me whether it is too huge to open:
/storage/quickbuild-data/configurations/246/reports/junit/XUnit/junit.h2.db
hi steve,
the master is solely for scheduling builds. so usually the load is not high. just check junit.h2.db. it is indeed hugh, 2.1G. how do i clean this? does "Artifact Cleanup Strategy" remove older reports?
No, "Artifact Cleanup Strategy" can not remove the older reports.
You can either remove the directory /storage/quickbuild-data/configurations/246/reports/junit/XUnit/ manually or deleting the report set on configuration Statistics page (in your case, XUnit report set).
i don't want to remove all history for the configuration though. is there anyway can i configure to keep 30 days of history?
You can rebuild the statistics data as the following page:
http://wiki.pmease.com/display/QB60/Reb ... ation+data
The statistics data size depends on how many builds in this configuration, so before rebuild statistics, you may need remove some useless builds first.
