AMQP transport ignores error from Rejected outcome.
Open
Stale
- Dominant language
- Java
- Stars
- 2.5k
- Forks
- 1.5k
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 79
Description
AmqpSender generates a MessageAck from Delivery. It would be nice if MessageAck.poisonCause was populated with data from Deliver.remoteState.error.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating AmqpSender and tracing how it creates MessageAck from Delivery, then inspect how a Rejected outcome exposes Deliver.remoteState.error. Determine how that error should populate MessageAck.poisonCause and add or run focused tests for the AMQP sender acknowledgement behavior. Done means the rejection error is preserved in the acknowledgement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100