Skip to content

Also check start.ini when resolving Jetty host and port - #256

Merged
robstryker merged 1 commit into
redhat-developer:masterfrom
robstryker:fix-jetty-port-detection
Aug 26, 2026
Merged

Also check start.ini when resolving Jetty host and port#256
robstryker merged 1 commit into
redhat-developer:masterfrom
robstryker:fix-jetty-port-detection

Conversation

@robstryker

Copy link
Copy Markdown
Collaborator

Summary

  • The Jetty port/host auto-detection only checked start.d/http.ini, missing the start.ini config location
  • When the port is configured in start.ini (e.g., jetty.http.port=9571), the resolver falls back to 8080, causing the startup poller to poll the wrong port and kill the server after the 2-minute timeout
  • Now also checks start.ini in the basedir as a fallback when start.d/http.ini does not contain the property
  • Users can also override the auto-detected values by setting the jetty.port and jetty.host server attributes directly

Fixes redhat-developer/vscode-rsp-ui#212

🤖 Generated with Claude Code

The Jetty port/host auto-detection only checked start.d/http.ini.
When the port is configured in start.ini instead (another standard
Jetty config location), the resolver falls back to 8080, causing the
startup poller to poll the wrong port. After the 2-minute timeout the
framework kills the server, even though it started successfully.

Check start.ini in the basedir as a fallback when start.d/http.ini
does not contain the property.

Users can also override the auto-detected values by setting the
jetty.port and jetty.host server attributes directly.

Fixes redhat-developer/vscode-rsp-ui#212

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@robstryker
robstryker merged commit cda8023 into redhat-developer:master Aug 26, 2026
3 checks passed
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.

Community Server Connector unexpectedly shuts down Jetty Server after 2 minutes

1 participant