Skip to content

fix: restore 120s timeout for jdtls initialize#48

Merged
aviadshiber merged 1 commit intomainfrom
fix/init-timeout
Apr 11, 2026
Merged

fix: restore 120s timeout for jdtls initialize#48
aviadshiber merged 1 commit intomainfrom
fix/init-timeout

Conversation

@aviadshiber
Copy link
Copy Markdown
Owner

Even module-scoped init can take >30s when the module has heavy Maven dependencies.

One-line change: send_request("initialize", ..., timeout=_INITIALIZE_TIMEOUT) with _INITIALIZE_TIMEOUT = 120s. Normal request timeout stays at 30s.

🤖 Generated with Claude Code

…ution)

Even module-scoped jdtls init can take >30s when the module has many
Maven dependencies that need classpath resolution on first cold start.
The 30s REQUEST_TIMEOUT was sufficient for simple workspaces but not
for production modules with heavy dependency trees.

_INITIALIZE_TIMEOUT = 120s applies only to the initialize handshake.
Normal request timeout stays at 30s.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@aviadshiber aviadshiber merged commit ff0f3f2 into main Apr 11, 2026
14 checks passed
@aviadshiber aviadshiber deleted the fix/init-timeout branch April 11, 2026 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants