SonarCloud background tasks failing

I got two projects failing on GC error:

Error Details
java.lang.OutOfMemoryError: GC overhead limit exceeded

Another project is failing on this error:

Error Details

java.lang.IllegalStateException: load called twice for thread 'Worker 0 (UUID=AWRgQJM7I66nRh8Y0hpU) on ce-worker-9' or state wasn't cleared last time it was used
	at com.google.common.base.Preconditions.checkState(Preconditions.java:197)
	at org.sonar.server.organization.DefaultOrganizationProviderImpl.load(DefaultOrganizationProviderImpl.java:73)
	at org.sonar.server.computation.organization.DefaultOrganizationLoader.start(DefaultOrganizationLoader.java:38)
	at sun.reflect.GeneratedMethodAccessor784.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.invokeMethod(ReflectionLifecycleStrategy.java:110)
	at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.start(ReflectionLifecycleStrategy.java:89)
	at org.picocontainer.injectors.AbstractInjectionFactory$LifecycleAdapter.start(AbstractInjectionFactory.java:84)
	at org.picocontainer.behaviors.AbstractBehavior.start(AbstractBehavior.java:169)
	at org.picocontainer.behaviors.Stored$RealComponentLifecycle.start(Stored.java:132)
	at org.picocontainer.behaviors.Stored.start(Stored.java:110)
	at org.picocontainer.DefaultPicoContainer.potentiallyStartAdapter(DefaultPicoContainer.java:1016)
	at org.picocontainer.DefaultPicoContainer.startAdapters(DefaultPicoContainer.java:1009)
	at org.picocontainer.DefaultPicoContainer.start(DefaultPicoContainer.java:767)
	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:135)
	at org.sonar.ce.task.container.TaskContainerImpl.bootup(TaskContainerImpl.java:77)
	at org.sonar.ce.task.projectanalysis.taskprocessor.ReportTaskProcessor.process(ReportTaskProcessor.java:71)
	at org.sonar.ce.taskprocessor.CeWorkerImpl.executeTask(CeWorkerImpl.java:135)
	at org.sonar.ce.taskprocessor.CeWorkerImpl.findAndProcessTask(CeWorkerImpl.java:98)
	at org.sonar.ce.taskprocessor.CeWorkerImpl.withCustomizedThreadName(CeWorkerImpl.java:82)
	at org.sonar.ce.taskprocessor.CeWorkerImpl.call(CeWorkerImpl.java:74)
	at org.sonar.ce.taskprocessor.CeWorkerImpl.call(CeWorkerImpl.java:44)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
1 Like

Hi Roy,

the compute engine, which processes reports, was impacted by an extremely large report sent to SonarCloud this night. Some nodes got crazy due to this out of memory error - while most remained OK. Things are back to normal, and we’ll be investigating how this happened.

Sorry for the inconvenience

1 Like

Alright then, thanks @Fabrice_Bellingard!

Is this fixed ? I’m also getting this error is latest SonarQube.

This thread is about a production incident that happened on SonarCloud, not SonarQube.