redhat-developer / redhat-developer/vscode-java
[vscode devcontainer] Language Support for Java (Syntax Server) client: couldn't create connection to server.
Nessuno ha ancora preso questa issue.
- Lingua principale
- TypeScript
- Stelle
- 2.3k
- Fork
- 546
- Merge medio
- 20h 1m
- PR unite (30g)
- 11
Descrizione
I use vscode devcontainer on a java project. Got the following error for the past month and couldn't get IntelliSense for java. Log file attached.
hs_err_pid939.log
Environment
- Operating System: Ubuntu 24.04 LTS on amd64
- JDK version: openjdk 21.0.3 2024-04-16 LTS OpenJDK Runtime Environment Temurin-21.0.3+9 (build 21.0.3+9-LTS) OpenJDK 64-Bit Server VM Temurin-21.0.3+9 (build 21.0.3+9-LTS, mixed mode, sharing)
- Visual Studio Code version:
Version: 1.90.0
Commit: 89de5a8d4d6205e5b11647eb6a74844ca23d2573
Date: 2024-06-04T19:34:48.028Z
Electron: 29.4.0
ElectronBuildId: 9593362
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.5.0 - Java extension version:v0.27.0
Steps To Reproduce
install docker desktop
clone the repo: https://github.com/zanqi/compiler
open it in vscode
vscode should popup a prompt on bottom right to open It in devcontainer. Click blue button to do so
after things settled (no more in progress UI on the screen), open a java file
"java: initialize workspace" in the bottom bar appears, but never finished. Click on it will see the error I am reporting.
[Please attach a sample project reproducing the error]
hs_err_pid939.log
Current Result
Got error on initializing language server
Expected Result
No error.
Additional Informations
Below is the top part of the error displayed in vscode output. Notice it is expecting jdk 17. But that's not the version installed by vscode devcontainer. Maybe that's issue? How to fix it?
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007ffffeec3a2d, pid=939, tid=991
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.11+9 (17.0.11+9) (build 17.0.11+9)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.11+9 (17.0.11+9, mixed mode, tiered, compressed oops, compressed class ptrs, parallel gc, linux-amd64)
# Problematic frame:
# V [libjvm.so+0xc87a2d] void OopOopIterateDispatch<PCIterateMarkAndPushClosure>::Table::oop_oop_iterate<InstanceKlass, narrowOop>(PCIterateMarkAndPushClosure*, oopDesc*, Klass*)+0xdd
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /workspaces/compiler/hs_err_pid939.log
#
# If you would like to submit a bug report, please visit:
# https://github.com/adoptium/adoptium-support/issues
#
[Error - 11:32:36 PM] Client Language Support for Java (Syntax Server): connection to server is erroring. Shutting down server.
[Error - 11:32:36 PM] Client Language Support for Java (Syntax Server): connection to server is erroring. Shutting down server.
[Error - 11:32:36 PM] Stopping server failed
Message: Cannot call write after a stream was destroyed
Code: -32099
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia con il file hs_err_pid939.log allegato e riproduci il problema usando il progetto zanqi/compiler in un devcontainer di VS Code con le versioni riportate di JDK e dell’estensione Java. Traccia l’inizializzazione dell’area di lavoro Java e la connessione di Language Support for Java (Syntax Server); il lavoro è completato quando il file Java viene inizializzato senza arresto anomalo del server né errore di connessione.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- docker, java, typescript, vscode
- Ambito
- developer-experience, devtools
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 25/100