redhat-developer / redhat-developer/vscode-java

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

Ouverte
#3,672 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Langage dominant
TypeScript
Étoiles
2.3k
Forks
546
Merge moyen
20 h 1 min
PR mergées (30 j)
11

Description

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

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Commencez par le fichier hs_err_pid939.log joint et reproduisez l’échec à l’aide du projet zanqi/compiler dans un devcontainer VS Code avec les versions signalées de JDK et de l’extension Java. Suivez l’initialisation de l’espace de travail Java et la connexion de Language Support for Java (Syntax Server) ; le travail est terminé lorsque le fichier Java s’initialise sans plantage du serveur ni erreur de connexion.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
docker, java, typescript, vscode
Domaine
developer-experience, devtools
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.