java.lang.OutOfMemoryError: Java heap space

Question

java.lang.OutOfMemoryError: Java heap space

kumarmohe opened this issue 4 years ago · comments

Hi,

We have recently installed this plug-in on our SonarQube Sever Community EditionVersion 7.9.2 (build 30863). When I tried to Code analysis of our Visual Studio DacPac project that has many .sql files (TSQL), its ending up with the errors shown in the attached file.

Sonar-SQL-Code-Analysis.txt

I tried setting the environment variable "SONAR_RUNNER_OPTS" in the build server as "-Xmx3062m -XX:MaxPermSize=512m -XX:ReservedCodeCacheSize=128m" and restarted it, but no use. The error still remains.

Prepare Analysis Task in TFS CI/CD Build Pipeline is set as "Use Standalone Scanner". However, it works fine when I use "Integrate with MSBuild" option. But Sonar documentation says, for doing this kind (SQL Code Analysis, Angular Code Analysis) of code analysis, it should be set as "Use Standalone Scanner".

Could you have a look and suggest any possible solution please?

Thanks,
Mohan

Mohan Jayabal · Answer 1 · Tue Aug 04 2020 22:56:27 GMT+0800 (China Standard Time)

@gretard I just wanted to bring to your notice.

gretard · Answer 2 · Wed Aug 05 2020 04:41:23 GMT+0800 (China Standard Time)

Hi, Maybe you could try to exclude that file or increase heap memory even further and reduce max perm size?

…

On Tue, Aug 4, 2020, 5:56 PM Mohan Jayabal ***@***.***> wrote: @gretard <https://github.com/gretard> I just wanted to bring to your notice. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE3VN7GDSG4ZJ4IUZYWZU5LR7AOSXANCNFSM4POZN3PQ> .

gretard · Answer 3 · Wed Aug 05 2020 04:44:46 GMT+0800 (China Standard Time)

Or maybe you could run sonar scanner directly with the configured memory options to see if errors persists. If not - mahbe sonar memory options were not passed from the build task.

…

On Tue, Aug 4, 2020, 11:41 PM Greta Rudžionienė ***@***.***> wrote: Hi, Maybe you could try to exclude that file or increase heap memory even further and reduce max perm size? On Tue, Aug 4, 2020, 5:56 PM Mohan Jayabal ***@***.***> wrote: > @gretard <https://github.com/gretard> I just wanted to bring to your > notice. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#10 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AE3VN7GDSG4ZJ4IUZYWZU5LR7AOSXANCNFSM4POZN3PQ> > . >

gretard · Answer 4 · Sat Aug 08 2020 16:20:22 GMT+0800 (China Standard Time)

Hi @kumarmohe - did you manage to solve this issue? :)

Mohan Jayabal · Answer 5 · Wed Aug 12 2020 01:29:43 GMT+0800 (China Standard Time)

Sorry @gretard . I was away from this for last a couple of days, so late response. This issue still exists. I tried increasing the heap memory, but no use. Our sonar server is running in Docker Container. Our Admin guys are trying to increase the memory for the container. I don't have direct access to the Sonar Qube Sever. Waiting for their response.

Almost all our .sql files are giving this issue. I am not sure anything wrong in those files.

gretard · Answer 6 · Wed Aug 12 2020 03:24:26 GMT+0800 (China Standard Time)

Hi,

Maybe this will help :) You need to specify environment variable named SONAR_SCANNER_OPTS instead of SONAR_RUNNER_OPTS.

I just tried to run commands as this on Windows:

set SONAR_SCANNER_OPTS=-Xmx3062m -XX:MaxPermSize=512m -XX:ReservedCodeCacheSize=128m
sonar-scanner.bat

And saw in the log file options being picked as this in the output:

OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was remov
ed in 8.0
INFO: Scanner configuration file: E:\darbai\sonar\sonar-scanner-cli-4.4.0.2170-w
indows\sonar-scanner-4.4.0.2170-windows\bin..\conf\sonar-scanner.properties
INFO: Project root configuration file: E:\darbai\sonar\samples\sql-server-sample
s-master\samples\databases\adventure-works\data-warehouse-install-script\sonar-p
roject.properties
INFO: SonarScanner 4.4.0.2170
INFO: Java 11.0.3 AdoptOpenJDK (64-bit)
INFO: Windows 8.1 6.3 amd64
INFO: SONAR_SCANNER_OPTS=-Xmx3062m -XX:MaxPermSize=512m -XX:ReservedCodeCacheSiz
e=128m

Please try this and check in the output if you see those options being picked :)

Mohan Jayabal · Answer 7 · Thu Aug 13 2020 03:19:30 GMT+0800 (China Standard Time)

I did as you suggested. Though I don't see "SONAR_SCANNER_OPTS" option in the log. But most of the Memory Heap issues are gone except for one file.

2020-08-12T18:54:41.3490614Z 14:54:41.331 INFO: SonarScanner 4.4.0.2170
2020-08-12T18:54:41.3491013Z 14:54:41.347 INFO: Java 1.8.0_261 Oracle Corporation (32-bit)
2020-08-12T18:54:41.3491226Z 14:54:41.347 INFO: Windows Server 2016 10.0 x86
2020-08-12T18:54:41.5132970Z 14:54:41.503 DEBUG: keyStore is :
2020-08-12T18:54:41.5133558Z 14:54:41.503 DEBUG: keyStore type is : jks
2020-08-12T18:54:41.5134036Z 14:54:41.503 DEBUG: keyStore provider is :
2020-08-12T18:54:41.5134226Z 14:54:41.503 DEBUG: init keystore

Now I see new set of errors as shown below.

2020-08-12T18:57:33.2410732Z 14:57:33.228 WARN: Unexpected exception while analyzing file: SQLDacPac/dbo/Stored Procedures/GetBudgetIncomeStatementActualsStats.sql
2020-08-12T18:57:33.2423645Z java.lang.ArrayIndexOutOfBoundsException: 1
2020-08-12T18:57:33.2760704Z at org.sonar.plugins.sql.sensors.sqlcheck.SQLCheckIssuesReader.read(SQLCheckIssuesReader.java:62)
2020-08-12T18:57:33.2761185Z at org.sonar.plugins.sql.sensors.SqlCheckSensor.execute(SqlCheckSensor.java:99)
2020-08-12T18:57:33.2761387Z at org.sonar.plugins.sql.sensors.SqlCheckSensor.access$000(SqlCheckSensor.java:23)
2020-08-12T18:57:33.2761600Z at org.sonar.plugins.sql.sensors.SqlCheckSensor$1.run(SqlCheckSensor.java:62)
2020-08-12T18:57:33.2761825Z at java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(Unknown Source)
2020-08-12T18:57:33.2762464Z at java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
2020-08-12T18:57:33.2762670Z at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(Unknown Source)
2020-08-12T18:57:33.2762851Z at java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)
2020-08-12T18:57:33.2763076Z at java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)
2020-08-12T18:57:33.2763199Z
2020-08-12T18:57:33.2763420Z 14:57:33.260 DEBUG: Running SQLCheck with [c:\program files\sql-check\sqlcheck.exe, -f, D:<Removed>_work\5\s\SQLDacPac\dbo\Stored Procedures\GetBudgetScenarioCopyExportData.sql, -v]
2020-08-12T18:57:34.2901597Z 14:57:34.275 WARN: Unexpected exception while analyzing file: SQLDacPac/dbo/Stored Procedures/GetBudgetIncomeStatementScenarios.sql
2020-08-12T18:57:34.2903279Z java.lang.ArrayIndexOutOfBoundsException: 1
2020-08-12T18:57:34.2906429Z at org.sonar.plugins.sql.sensors.sqlcheck.SQLCheckIssuesReader.read(SQLCheckIssuesReader.java:62)
2020-08-12T18:57:34.2910381Z at org.sonar.plugins.sql.sensors.SqlCheckSensor.execute(SqlCheckSensor.java:99)
2020-08-12T18:57:34.2984594Z at org.sonar.plugins.sql.sensors.SqlCheckSensor.access$000(SqlCheckSensor.java:23)
2020-08-12T18:57:34.2985751Z at org.sonar.plugins.sql.sensors.SqlCheckSensor$1.run(SqlCheckSensor.java:62)
2020-08-12T18:57:34.2986141Z at java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(Unknown Source)
2020-08-12T18:57:34.2986445Z at java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
2020-08-12T18:57:34.2986690Z at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(Unknown Source)
2020-08-12T18:57:34.2986947Z at java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)
2020-08-12T18:57:34.2987184Z at java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)
2020-08-12T18:57:34.2987614Z

I have attached complete log below.

Thanks for your support.

Thanks,
Mohan

Sonar-SQL-Code-Analysis.txt

gretard · Answer 8 · Tue Aug 18 2020 00:58:08 GMT+0800 (China Standard Time)

Hi, I found an issue with SQLCheck sensor. Please try the latest version https://github.com/gretard/sonar-sql-plugin/releases/tag/1.1.0

Mohan Jayabal · Answer 9 · Wed Aug 19 2020 23:07:02 GMT+0800 (China Standard Time)

Sure. Will try it. Thanks.

Mohan Jayabal · Answer 10 · Wed Sep 02 2020 05:05:35 GMT+0800 (China Standard Time)

We have deployed the new version. Testing is going on. I will update once its done.