redhat-developer / redhat-developer/vscode-java

Error connecting to server

Open
#1,566 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

Hi,
I've installed the extension for first time, and when it starts it shows an error "The Language Support for Java server crashed".
It opens the server logs indicating:
java.lang.IllegalAccessError: tried to access method org.eclipse.jdt.ls.core.internal.highlighting.SemanticHighlightings$AutoboxHighlighting.()V from class org.eclipse.jdt.ls.core.internal.highlighting.SemanticHighlightings

I've tried disabling semantic highlighting, and cleaning the workspace w/out success.

Environment
  • Operating System:
    linux debian base distro : Linux XXXX 4.15.0-29deepin-generic

  • JDK version:
    openjdk version "11" 2018-09-25
    OpenJDK Runtime Environment (build 11+13-Debian-2)
    OpenJDK 64-Bit Server VM (build 11+13-Debian-2, mixed mode, sharing)

  • Visual Studio Code version:
    Version: 1.47.3
    Commit: 91899dcef7b8110878ea59626991a18c8a6a1b3e
    Date: 2020-07-23T15:51:39.791Z
    Electron: 7.3.2
    Chrome: 78.0.3904.130
    Node.js: 12.8.1
    V8: 7.8.279.23-electron.0
    OS: Linux x64 4.15.0-29deepin-generic

  • Java extension version:
    v0.65.0

Steps To Reproduce
  1. Install VSCode and the extension
  2. Open any .java file, in the bottom right there's a spinning circle that ends up showing the error

I am attaching the log from the server. Please let me know if I am missing any useful information.

Additional Informations

Not sure if it adds any context, but I initially got the Java Extension Pack by sync configurations from another windows based vscode. I use "Settings Sync" extension. After getting this issue, I manually removed these packages and installed only the Language Support one but the issue persists.
vscode-java.error.txt

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

Review the attached vscode-java.error.txt and the SemanticHighlightings stack trace, then reproduce the crash by opening any .java file with the listed VS Code, JDK, and extension versions. Determine why the language server fails to start and verify that opening a Java file completes without the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript, vscode
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.