Skip to content

Conversation

@BenchmarkingBuffalo
Copy link
Contributor

For WebSocket support the preconfigured ThreadExecutor is set for ChannelRegistrations similar to the JpaRepositoriesAutoConfiguration.

See gh-39314

For WebSocket support the preconfigured ThreadExecutor is set for ChannelRegistrations similar to the JpaRepositoriesAutoConfiguration.

See spring-projectsgh-39314
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 17, 2024
@BenchmarkingBuffalo BenchmarkingBuffalo force-pushed the 39314-websocket-virtual-threads branch from 1c2d6c4 to e9bf2b3 Compare February 19, 2024 17:38
@mhalbritter mhalbritter changed the title Configure suitable TaskExecutor for WebSocket Configure suitable TaskExecutor for WebSocket when virtual threads are enabled Feb 20, 2024
@mhalbritter mhalbritter added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Feb 20, 2024
@mhalbritter mhalbritter self-assigned this Feb 20, 2024
@mhalbritter mhalbritter added this to the 3.3.x milestone Feb 20, 2024
mhalbritter pushed a commit that referenced this pull request Feb 20, 2024
For WebSocket support the preconfigured ThreadExecutor is set for
ChannelRegistrations similar to the JpaRepositoriesAutoConfiguration.

See gh-39611
@mhalbritter mhalbritter modified the milestones: 3.3.x, 3.3.0-M2 Feb 20, 2024
@mhalbritter
Copy link
Contributor

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: enhancement A general enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants