[BUG] Using the Java LSP server fails because option "startupTimeout" is not supported
Status Fixed / completed
Reported on v2.1.1
Maintainer reply ✓ Yes — ashwin-ant
Activity 5 comments · opened Jan 8, 2026 · closed Apr 18, 2026
💡 Likely answer: A maintainer (ashwin-ant, collaborator)
responded on this thread — see the highlighted reply below.
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
On startup the Java LSP server fails to load. It fails because the ~/.claude/plugins/marketplaces/claude-plugins-official/.claude-plugin/marketplace.json defines an option named startupTimeout which does not appear to be supported for Java. Removing this option causes the server to load and it is available.
What Should Happen?
The java LSP server should load and be available.
Error Messages/Logs
Error: Error: Failed to initialize LSP server plugin:jdtls-lsp:jdtls: LSP server 'plugin:jdtls-lsp:jdtls': startupTimeout is not yet implemented. Remove this field from the configuration.
Steps to Reproduce
- Install the Java LSP plugin
jdtls-lsp - Make sure that it's enabled
- Start a new session with
claude --debug - Look at the debug log for the above error
- Edit
~/.claude/plugins/marketplaces/claude-plugins-official/.claude-plugin/marketplace.jsonand remove thestartupTimeoutoption from thejdtls-lspplugin settings. - Start a new session with
claude --debug - Look in log and verify error does not appear.
- For Claude to use the LSP tool to verify it is working correctly.
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.1
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Warp
Additional Information
_No response_
5 Comments
Same issue with the Kotlin LSP
Can confirm the issue
The issue is still occurring
This was fixed in v2.1.50 — The LSP
startupTimeoutoption is now implemented instead of throwing 'not yet implemented'. If you're still seeing this in the latest version, please comment with your version and repro and we'll reopen.This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.