redhat-developer / redhat-developer/vscode-java

Error occurred in initializing language server when opening Multi Module Maven Project in vscode

Open
#2,806 18 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ls-error/crash Maven
Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

Type: Bug

I checked out a Maven Project with multiple modules (main POM.xml and nested project with POM.xml files) and was able to open the project and compile it correctly using Eclipse.

However, if I check out the same project in another folder and open the project in vscode I will get an error while building the project while it is still loading. I even tried opening the same project folder that was built successfully in Eclipse, but I get the same error in vs code.

In the vscode status bar, I see the message "Error occurred in initializing language server". Then if I click on the thumbs-own icon, I see two log files which are attached below:

.log
client.log

Extension version: 0.25.6
VS Code version: Code 1.73.1 (6261075646f055b99068d3688932416f2346dd3b, 2022-11-09T04:27:29.066Z)
OS version: Windows_NT x64 10.0.19042
Modes:
Sandboxed: No

System Info
Item Value
CPUs Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz (4 x 2904)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Load (avg) undefined
Memory (System) 15.88GB (2.09GB free)
Process Argv --crash-reporter-id 18a83e5c-0407-4a13-8d26-c6c9570eedd6
Screen Reader no
VM 0%
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1:30587005
fc301958:30595537
282f8724:30602487
gswce1:30612156
3d0df643:30613357
dbltrim-noruby:30604474
f6dab269:30613381

Extensions (37)
Extension Author (truncated) Version
vscode-tomcat ada 0.12.1
Bookmarks ale 13.3.1
atlascode atl 2.10.12
vscode-log-viewer ber 0.12.2
vscode-eslint dba 2.2.6
xml Dot 2.5.1
vscode-html-css ecm 1.13.1
packsharp els 2.3.2
open-lnk Enk 0.0.1
dotnet-test-explorer for 0.7.8
vscode-nuget-package-manager jmr 1.1.6
svn-scm joh 2.15.5
json-escaper jos 1.1.2
vscode-JS-CSS-HTML-formatter lon 0.2.3
csharp ms- 1.25.2
data-workspace-vscode ms- 0.3.0
mssql ms- 1.16.0
sql-bindings-vscode ms- 0.3.0
sql-database-projects-vscode ms- 0.19.0
powershell ms- 2022.11.0
sqltools mtx 0.26.0
sqltools-driver-mssql mtx 0.3.0
java-string-literal-tools pol 1.0.1
fabric8-analytics red 0.3.6
java red 1.12.0
vscode-commons red 0.0.6
vscode-yaml red 1.10.1
LiveServer rit 5.7.9
vscode-fileutils sle 3.5.0
code-spell-checker str 2.11.0
intellicode-api-usage-examples Vis 0.2.6
vscodeintellicode Vis 1.2.29
vscode-java-debug vsc 0.46.0
vscode-java-dependency vsc 0.21.1
vscode-java-pack vsc 0.25.6
vscode-java-test vsc 0.37.1
vscode-maven vsc 0.39.2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the attached default.log and client.log, then reproduce the failure with a multi-module Maven project in VS Code using the reported extension and VS Code versions. Trace the language-server initialization failure and verify that the project opens and loads without the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.