getsentry / getsentry/sentry-java
`AsyncHttpTransport` connection reuse
Open
Feature
Java
Platform: Java
- Dominant language
- Kotlin
- Stars
- 1.4k
- Forks
- 478
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 67
Description
### Problem Statement
Sentry `AsyncHttpTransport` closes the connection after each envelope sent.
This may cause problems on high traffic servers / cloud environments.
Came up in https://github.com/getsentry/sentry-java/issues/6000
### Solution Brainstorm
We could reuse the connection / not close unless there's an error.
Contributor guide
Research direction
Start by locating AsyncHttpTransport and tracing where the connection is closed after an envelope is sent. Review the related Sentry issue 6000 and the transport's existing error handling; done means connections are reused between envelopes and still close when an error requires it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100