Update for ECJ required: Error "array store with invalid types" in ECJ since LTA 2025.1

SonarQube Server / Community Build
, ,
1

Server Information:

  • SonarQube Enterprise Edition v2025.1 (102418), Gradle using Gradle - Plugin: org.sonarqube
  • Deploy: Docker
  • Trying to do what: Run SonarQube analysis against a project

We updated our staging instance from v10.7 to LTA 2025.1 and now encounter the following issue: AssertionError: array store with invalid types at org.eclipse.jdt.internal.compiler.codegen.OperandStack.xastore by srikanth-sankaran · Pull Request #3644 · eclipse-jdt/eclipse.jdt.core · GitHub
We skipped v10.8, so I don’t know if that version is also affected as I didn’t check which ECJ version is used there.

I don’t think I need to attach any logs, as the link to the fix should be self-explanatory. In regards to the issue within an analysis run, the execution stops and throws an exception with “array store with invalid types”. If there is anything I can provide or you need from me, please tell me.

As this has been fixed in ECJ can you please release an update to SonarQube Server (or whatever is needed…) with the a newer ECJ version?

As this prevents us from updating our production SQ Server instance to the newest version, it would be great if you could give me some time frame until when you plan on fixing this or you have any possible workaround for me.

Thanks.

2

Hi,

Could we have a --info log anyway, please?

 
Thx,
Ann

3

Hi @ganncamp, thanks for the reply.

Could you point me in the right direction for the --info you are looking for? Are you talking about the log level option here? Analysis parameters | SonarQube Server Documentation

If it is about the analysis itself, maybe you could give me the Gradle command you expect including all necessary (logging) parameters.

Thanks!

4

Hi,

Gradle logs are remarkably terse by default. I was asking that you add --info to your grade command to get INFO-level logging from the job.

 
Thx,
Ann

6

Hi,

In parallel, we’ve discovered there’s a bug in the version of JDT we’re using. We’re on it and thanks for your report!

 
Ann

8

Hi Ann,
thanks for getting back. Is it the same bug I linked in my post above or a different one? Just to be on the same page, in case there is another bug we should be wary about while testing SQ 2025.1 further.

I will provide the --info log tomorrow (need to strip it a bit).

Thanks.

9

Hi,

The same bug.

 
Ann

11

Hi @ganncamp,
as you have reproduced it already anyways and found the issue, the log is probably not that helpful anymore. I thought about including it anyways as it was requested, but even after limiting it to “–info” I would have to spend a lot of time cutting out private information. If it is needed, I’ll see what I can do but I’d rather not spend time on it, to be honest.

Digging through your public tickets I can see that the ECJ was updated via: Jira

Is there any chance this is brought to a version older than SQ 2025.3? If not, is there an expected 2025.3 release date?

If 2025.3 isn’t happening any time soon, is there by chance anything (minimally invasive) I can do to get the update working? Considering we pay for SQ Enterprise I would like to utilize the newest available version (2025.2) and update regularly. Maybe someone has an idea of how we can update regardless of this issue?

Thanks.

12

Hi,

2025.3 is expected at the end of this month.

 
HTH,
Ann