Skip to content

Consider "RMI Runtime" thread group as a user group#972

Draft
trancexpress wants to merge 1 commit into
eclipse-jdt:masterfrom
trancexpress:gh971
Draft

Consider "RMI Runtime" thread group as a user group#972
trancexpress wants to merge 1 commit into
eclipse-jdt:masterfrom
trancexpress:gh971

Conversation

@trancexpress

@trancexpress trancexpress commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

LSP4J calls are serviced by the "RMI Runtime" thread group. In JDK code, this group is considered a user thread group, as it can run user code (such as LSP4J calls from clients).

This change adjusts JDIThread to consider the "RMI Runtime" thread group as a user thread group. This makes it possible to debug LSP4J code without turning on the system threads Debug view filter. Which in turn avoids running into Debug view updating mechanism bugs related to using filters.

See: #971

LSP4J calls are serviced by the "RMI Runtime" thread group.
In JDK code, this group is considered a user thread group,
as it can run user code (such as LSP4J calls from clients).

This change adjusts JDIThread to consider the "RMI Runtime"
thread group as a user thread group. This makes it possible
to debug LSP4J code without turning on the system threads
Debug view filter. Which in turn avoids running into
Debug view updating mechanism bugs related to using filters.

See: eclipse-jdt#971
@trancexpress

Copy link
Copy Markdown
Contributor Author

@HannesWell is there something wrong with the bot that bumps versions? Or its only running for the platform and not for JDT?

@iloveeclipse

Copy link
Copy Markdown
Member

It's also broken on platform

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