EntryNotFound error on redhat.java when starting up

[halloleo]

I have installed the current vscode-java-pack (v 0.29.202...). HWen I start up VS Cide with a jaav file I get the following in the Extension Host Output panel:

2025-03-31 17:19:38.975 [info] Extension host with pid 3725824 started
2025-03-31 17:19:38.975 [info] Skipping acquiring lock for /home/me/.config/Code/User/workspaceStorage/16648c344a3bfbe1694808f8d65bed2f.
2025-03-31 17:19:39.222 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2025-03-31 17:19:39.275 [info] ExtensionService#_doActivateExtension vscjava.vscode-java-pack, startup: false, activationEvent: 'onLanguage:java'
2025-03-31 17:19:39.880 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2025-03-31 17:19:40.000 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2025-03-31 17:19:40.237 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2025-03-31 17:19:40.407 [info] Eager extensions activated
2025-03-31 17:19:40.475 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2025-03-31 17:19:40.480 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2025-03-31 17:19:50.829 [error] EntryNotFound (FileSystemError): Error: ENOENT: no such file or directory, scandir '/home/me/.config/Code/User/workspaceStorage/16648c344a3bfbe1694808f8d65bed2f/redhat.java'
	at Ji.e (file:///usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:114:9057)
	at Object.readDirectory (file:///usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:114:7197)

So I get on extension startup an "EntryNotFound" error for the redhat.java file. How can I fix this?

All pointers are very much appreciated!

I'm running VS Code 1.95 on RHEL 9.4

[github-actions]

Hi @halloleo, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Workarounds

• Clear the corrupted Workspace Storage for this project. In your terminal run:

  rm -rf ~/.config/Code/User/workspaceStorage/16648c344a3bfbe1694808f8d65bed2f

  The folder will be recreated on next VS Code launch.
• If the above doesn’t help, clear all workspace storage cache:

  rm -rf ~/.config/Code/User/workspaceStorage

• Reinstall the Java language support extension to regenerate missing files:
  1. Open Extensions panel in VS Code
  2. Search for Language Support for Java by Red Hat (redhat.java)
  3. Uninstall → Reload → Install
• Verify that ~/.config/Code/User/workspaceStorage and its subfolders are writable by your user.

Duplicate

• Bug: extension does not startup with errors on extension host #1488

Other references with low confidence

No additional references found.

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

[chagong]

The EntryNotFound on workspaceStorage/<hash>/redhat.java is a symptom, not the root cause. That path is redhat.java's per-workspace storage folder, which VS Code creates lazily (on first write). Early activation code touches it — most notably the heap-dump watcher set up in registerOutOfMemoryDetection(storagePath) — so if the folder doesn't exist yet, the readDirectory/scandir logs EntryNotFound.

What matters is why the folder is never created: redhat.java aborts before the language server starts, so jdt_ws (and the storage dir) are never written. On RHEL 9.4 this is almost always a JDK/requirements issue — no compatible JDK, a stale java.jdt.ls.java.home/JAVA_HOME, or a platform-agnostic VSIX missing the bundled JRE. The JDT-LS in this build requires Java 21+ to run the server.

To confirm: check Output → "Language Support for Java" and run Java: Open Java Language Server log file. If those show a requirements/JDK error (or are empty), that's the real failure. Clearing workspaceStorage won't help, since it doesn't address the startup failure.