redhat-developer / redhat-developer/vscode-java

java.lang.IllegalArgumentException Attempted to endRule & - java.lang.IllegalArgumentException Worker thread ended job: Classpath Update Job(29039), but still holds rule

Offen
#3,997 14 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Gradle
Vorherrschende Sprache
TypeScript
Sterne
2.3k
Forks
546
Ø Merge
20 Std. 1 Min.
Gemergte PRs (30 T.)
11

Beschreibung

Hi,
We have a multi-module Gradle-based Java Spring application. When trying to open it in Cursor IDE with the Language Support for Java plugin enabled, the project does not fully load.

We had a circular dependency issue which i reported in https://github.com/microsoft/vscode-gradle/issues/1659 and https://github.com/redhat-developer/vscode-java/issues/3986 but it seems with Language Support for Java(TM) by Red Hat plugin Version 1.41.0, our gradle sub projects are visible as expected, without circular dependencies reported and without weird project names.

But now, with Language Support for Java(TM) by Red Hat plugin Version 1.41.0, when i open my project even java projects are visible in JAVA PROJECTS view, the code is not loaded, not detected properly after waiting for some hours.

I see the following kind of errors logged for plugin. There are too many logged errors. I am putting here just some samples.

[Error - 11:56:38] 31 Mar 2025, 11:56:38 An internal error occurred during: "Classpath Update Job".
Attempted to endRule: null, does not match most recent begin: R/.  See log for trace information if rule tracing is enabled.
java.lang.IllegalArgumentException: Attempted to endRule: null, does not match most recent begin: R/.  See log for trace information if rule tracing is enabled.
	at org.eclipse.core.runtime.Assert.isLegal(Assert.java:68)
	at org.eclipse.core.internal.jobs.ThreadJob.illegalPop(ThreadJob.java:126)
	at org.eclipse.core.internal.jobs.ThreadJob.pop(ThreadJob.java:391)
	at org.eclipse.core.internal.jobs.ImplicitJobs.end(ImplicitJobs.java:118)
	at org.eclipse.core.internal.jobs.JobManager.endRule(JobManager.java:799)
	at org.eclipse.core.internal.resources.WorkManager.checkOut(WorkManager.java:174)
	at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1605)
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:50)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

[Error - 11:56:38] 31 Mar 2025, 11:56:38 Worker thread ended job: Classpath Update Job(29039), but still holds rule: ThreadJob(Classpath Update Job(29039),[R/])
Worker thread ended job: Classpath Update Job(29039), but still holds rule: ThreadJob(Classpath Update Job(29039),[R/])
java.lang.IllegalStateException: Worker thread ended job: Classpath Update Job(29039), but still holds rule: ThreadJob(Classpath Update Job(29039),[R/])
	at org.eclipse.core.internal.jobs.ImplicitJobs.endJob(ImplicitJobs.java:139)
	at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:119)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:83)

Our installed versions;
OS Version: macos 15.3.2 (24D81)
Gradle: 8.12.1
Java: OpenJDK 21.0.3 LTS
Spring Boot: 3.4.3
Cursor Version: 0.47.8 (Universal)
Language Support for Java(TM) by Red Hat plugin Version 1.41.0
vscode-gradle Extension Version: 3.16.4

It looks like the issue is related to latest Language Support for Java(TM) by Red Hat plugin Version 1.41.0 version.
Can you please have a look ?

Thanks in advance
Ramazan

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Beginne damit, das mehrmodulige Gradle-Projekt mit den aufgeführten Versionen von Java, Cursor und Language Support for Java zu reproduzieren, und untersuche dann die Fehler des Classpath Update Job. Verfolge den gemeldeten Pfad durch JobManager.endRule, WorkManager.checkOut und Workspace.endOperation. Als erledigt gilt die Aufgabe, wenn das Projekt ohne die Regelabweichungs- und Worker-Thread-Fehler korrekt geladen wird.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
java, spring, vscode
Bereich
build-system, devtools
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
30/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.