redhat-developer / redhat-developer/vscode-java
Error: The Language Support for Java server crashed 5 times in the last 3 minutes. The server will not be restarted.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
This extension cannot start successfully and popup this error message. I found some logs in the output, hope it can help:
[Info - 11:24:22 AM] Connection to server got closed. Server will restart.
[Info - 11:24:23 AM] Connection to server got closed. Server will restart.
[Warn - 11:24:24 AM] Dec 6, 2016 11:24:24 AM The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
[Info - 11:24:25 AM] Connection to server got closed. Server will restart.
[Warn - 11:24:26 AM] Dec 6, 2016 11:24:26 AM The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
[Info - 11:24:26 AM] Connection to server got closed. Server will restart.
[Warn - 11:24:27 AM] Dec 6, 2016 11:24:27 AM The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
[Error - 11:24:27 AM] Connection to server got closed. Server will not be restarted.
Environment
- Operating System: Windows 7 Enterprise
- JDK version: 1.8.0_40 (Setting JAVA_HOME environment variable only)
- Visual Studio Code version: 1.7.2
- Java extension version: 0.0.7
Steps To Reproduce
- Download and install vscode 1.7.2
- Search and install this extension: Language Support for Java(TM) by Red Hat
- Open a .java file to start this extension
- (Optional) Check the popup message and output logs
Additional Informations
I installed the same-version vscode and extension to another machine whose system is Windows 10, and the extension can work as expected.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crash using the listed VS Code 1.7.2, Java extension 0.0.7, JDK 1.8.0_40, and Windows 7 steps, then inspect the language-server output for the repeated connection closures and workspace recovery warnings. Done means the Java extension starts successfully and no longer reaches the five-crash shutdown state.
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
- Mostly clear
- Newbie friendliness
- 35/100