redhat-developer / redhat-developer/vscode-java

[vscode devcontainer] Language Support for Java (Syntax Server) client: couldn't create connection to server.

Abierto
#3,672 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
TypeScript
Estrellas
2.3k
Forks
546
Merge medio
20 h 1 min
PR fusionados (30 d)
11

Descripción

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

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Comienza con el archivo hs_err_pid939.log adjunto y reproduce el fallo usando el proyecto zanqi/compiler en un devcontainer de VS Code con las versiones indicadas de JDK y de la extensión de Java. Rastrea la inicialización del espacio de trabajo de Java y la conexión de Language Support for Java (Syntax Server); se considera terminado cuando el archivo Java se inicializa sin que el servidor se bloquee ni se produzca un error de conexión.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
docker, java, typescript, vscode
Área
developer-experience, devtools
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.