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.

Outofmemory since 6.1.30 update #3667

jossy ·
Hi.

We constantly get a OOM Error every around 2 days since we upgraded from v6.1.23 to v6.1.30. After the Error all requests return a "out of heap space" error message, so QB is basically broken until we restart the server. Is this happening for other customers too? Is there some change in which might cause this? Has anyone an idea what we can check?

We're running QB on Ubuntu with 16 GB heap and G1GC.

Edit: Another thing, maybe related: We get an exception in the snapshot taking:
com.pmease.quickbuild.QuickbuildException: java.lang.RuntimeException: java.lang.InterruptedException
at com.pmease.quickbuild.util.WaitableHashMap.waitFor(WaitableHashMap.java:93)
at com.pmease.quickbuild.grid.NodeServiceImpl.getBuildId(NodeServiceImpl.java:245)
at com.pmease.quickbuild.dependency.TriggerForLatestFinishedResolver.getDependency(TriggerForLatestFinishedResolver.java:136)
at com.pmease.quickbuild.dependency.TriggerForLatestFinishedResolver$$EnhancerByCGLIB$$fae2ed28.CGLIB$getDependency$3(<generated>)
at com.pmease.quickbuild.dependency.TriggerForLatestFinishedResolver$$EnhancerByCGLIB$$fae2ed28$$FastClassByCGLIB$$b5b0e177.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:215)
at com.pmease.quickbuild.DefaultScriptEngine$Interpolator.intercept(DefaultScriptEngine.java:261)

Do you know why this might happen?

Regards,
Alex
  • replies 1
  • views 1624
  • stars 0
robinshen ADMIN ·
Please make sure to upgrade to 6.1.33 as 6.1.30 has a serious issue of heavy resource usage due to an artifact cleanup bug.