micronaut-projects / micronaut-projects/micronaut-rxjava3
Rx3SseClient got disconnect after 5 mins
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5
- Forks
- 4
- Avg merge
- 3h 36m
- Merged PRs (30d)
- 8
Description
### Expected Behavior
Do not disconnect if server keep sending heartbeat, so the connection should be keep-alive.
### Actual Behaviour
The sse client got disconnect after 5 mins, it was trigger by the WriterIdleTimeoutHandler in IdleStateHandler from Netty.
The idleStateHandler was added by [https://github.com/micronaut-projects/micronaut-core/blob/v3.7.5/http-client/src/main/java/io/micronaut/http/client/netty/ConnectionManager.java#L609](url)
### Steps To Reproduce
Here is my client:
`Rx3SseClient.create(URL)
.eventStream()
.subscribe()
`
### Environment Information
_No response_
### Example Application
_No response_
### Version
2.4.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked http-client/netty/ConnectionManager.java around line 609 and inspect how Netty's IdleStateHandler handles the SSE connection. Reproduce with Rx3SseClient.create(URL).eventStream() while the server sends heartbeats. Done means the client remains connected beyond five minutes when heartbeats continue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100