Very slow in Version 11.4 with many messages in Console log

SonarQube for IDE Eclipse
1

Please provide

  • Operating system: Windows
  • IDE name and version: Eclipse 2025-03
  • SonarQube for Eclipse plugin version: 11.4
  • Programming language you’re coding in: java
  • Is connected mode used:no

Console Log being filled with the following and it takes forever to run
The following is only a SMALL snaphot. It makes v11.4 unusable.

Number of blame output sections is higher than expected number of lines. Section content: src/classmcs/gui/statistics/jFreeChart/ChartPanel.java

}

529083edd8683ceeddb90070ff318a8934846c8a 453 438

author Robert Wolf

author-mail Robert_Wolf@amat.com

author-time 1711739308

author-tz -0700

committer Robert Wolf

committer-mail Robert_Wolf@amat.com

committer-time 1711739308

committer-tz -0700

summary MCS-17424 WebUI: Fix LocationState for disabled shelves when UI is refreshed.

boundary

Number of blame output sections is higher than expected number of lines. Section content: src/classmcs/gui/statistics/jFreeChart/ChartPanel.java

}

529083edd8683ceeddb90070ff318a8934846c8a 454 439

author Robert Wolf

author-mail Robert_Wolf@amat.com

author-time 1711739308

author-tz -0700

committer Robert Wolf

committer-mail Robert_Wolf@amat.com

committer-time 1711739308

committer-tz -0700

summary MCS-17424 WebUI: Fix LocationState for disabled shelves when UI is refreshed.

boundary

Number of blame output sections is higher than expected number of lines. Section content: src/classmcs/gui/statistics/jFreeChart/ChartPanel.java

}

529083edd8683ceeddb90070ff318a8934846c8a 455 440

author Robert Wolf

author-mail Robert_Wolf@amat.com

author-time 1711739308

author-tz -0700

committer Robert Wolf

committer-mail Robert_Wolf@amat.com

committer-time 1711739308

committer-tz -0700

summary MCS-17424 WebUI: Fix LocationState for disabled shelves when UI is refreshed.

boundary

Number of blame output sections is higher than expected number of lines. Section content: src/classmcs/gui/statistics/jFreeChart/ChartPanel.java

}

Number of blame output sections is higher than expected number of lines. Section content: src/classmcs/server/XMLSoap/nothot/activityManager/ClassMCSServiceHandler.java

}

Number of blame output sections is higher than expected number of lines. Section content: src/classmcs/emulator/script/command/device/DeleteCarrierCustomPropertyCommand.java

}

Number of blame output sections is higher than expected number of lines. Section content: src/classmcs/lib/service/carrier/CommandMoveRequestsGet.java

Number of blame output sections is higher than expected number of lines. Section content: src/classmcs/gui/alternates/AlternateGroupNode.java

}

Number of blame output sections is higher than expected number of lines. Section content: src/webui/src/app/shared/types/events/webapp/widget-status.event.ts

}

Number of blame output sections is higher than expected number of lines. Section content: src/classmcs/server/messoap/emulator/standard/gui/interfaces/DeviceStatusListReply.java

}

Number of blame output sections is higher than expected number of lines. Section content: config/MCDFiles/MurataIBSEM350.mcd

Number of blame output sections is higher than expected number of lines. Section content: src/classmcs/server/custom/CustomPropertyStatisticalData.java

}

Number of blame output sections is higher than expected number of lines. Section content: src/classmcs/lib/service/customProperties/CommandCustomPropertiesModify.java

}

Number of blame output sections is higher than expected number of lines. Section content: src/webui/src/app/device/shelf-carriers-card/shelf-carriers-card.component.spec.ts

});

Number of blame output sections is higher than expected number of lines. Section content: src/classmcs/server/XMLSoap/nothot/activityManager/interfaces/DeviceLogicalStateChangeReply.java

}

2

It may be related to " * Improve indexing of project to not exclude base directory"
since in Eclipse we exclude the folder “webui/” which has many many files. Sonar should follow the exclude in the Eclipse Project Build Path source

3

Reverted to plugin version 11.3 and everything is back to normal.

4

Hi @dandoy,

thanks for reaching out. The issues you face has something to do with an internal rework, for that I’ll ping my colleagues! Can you please provide a full log if possible?

Regarding file exclusions, there is an option to exclude files via the preferences the plug-in provides. There is an extra step to not only exclude these files from the analysis, but also for indexing, for which we have a not yet planned ticket.

We currently do not cover the exclusions/inclusions provided by JDT, I guess you mean these ones:

Screenshot from 2025-04-01 09-02-04
Screenshot from 2025-04-01 09-02-041005×647 70.5 KB

Could you please share with me why you exclude files like this? From my understanding this excludes files from compilation as well.

Best,
Tobias

8

We exclude files in that folder because they are NOT java files. They are .ts, .scss, .html.

It may be the Sonar indexing that is taking a long time. We have always had those files there and it may have slowed down the indexing in previous versions, but not to this extent and we never got 1000s of these messages “Number of blame output sections is higher than expected number of lines.” in previous versions.

9

Of course I am just guessing what the issue may be, but I do know the biggest difference between 11.3 and 11.4 is the plethora of “Number of blame output sections is higher than expected number of lines.” messages in 11.4.

10

Thank you very much for the info! I’ll write this down and will have a look if this is something we want or not - meaning if we rather want to rely on our own exclusion option.

On the contrary, we also analyze TypeScript, CSS, and HTML with our analyzers - just a heads up. If you still want to not analyze them, I would advise you to exclude them as I linked above for now.

11

But is that really the problem, since I have not changed anything and there is a difference between 11.3 and 11.4. I think there still may be a problem with 11.4 with it logging so many of those messages that don’t have anything to do with the excluded files, I think there may still be some issue with 11.4.

12

Hi @dandoy,

sorry for the confusion, this is not related to the issue you are facing that is currently with another colleague. Since it is not an error, this can be ignored - but the thing being very noisy and annoying is a thing to be changed, indeed.

My questions are out of curiosity to better understand your use case of this JDT specific exclusion and the reasoning behind it and for me to link it to possible, other improvements we can do to our plug-in :nerd_face:
I should have been a bit more clearer of what I wanted to achieve with my questionnaire here.

Best,
Tobias

13

Thanks, not only is the message noisy and annoying, it seems to slow down Sonar so that it is unusable since it takes a long time for it to log all those messages so I had to revert to 11.3

FYI: We don’t analyze those non-java files in Eclipse since developers working on those files develop in a different IDE environment. They also use Sonar in that environment.

1 Like
14

Hello @dandoy.

Thanks for your report. Here’s the ticket for this. Logging is too wordy indeed. It should be fixed in one of the next versions.

Best,