spring-projects / spring-projects/spring-integration
Republish ErrorMessage [INT-4287]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 1.2k
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 62
Description
Gary Russell opened INT-4287 and commented
If an ErrorMessage is sent to an outbound channel adapter, and the message contains an AMQP_RAW_MESSAGE header, republish the message in a similar manner to the Spring AMQP RepublishMessageRecoverer including exception information in headers.
Then, adding an outbound adapter can be seamlessly subscribed to the inbound endpoint error channel to get republish to DLQ behavior.
This will likely need a minor change in Spring AMQP to move the X_* headers from the recoverer to a utility class. Although, they are public so maybe it's ok to leave them there. On the other hand, they should probably become first class properties of MessageProperties.
No further details from INT-4287
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 outbound channel adapter handling an ErrorMessage containing the AMQP_RAW_MESSAGE header, and compare the desired behavior with Spring AMQP's RepublishMessageRecoverer. Review how the recoverer exposes X_* headers and how MessageProperties could represent them. Done means an outbound adapter can republish the error message with exception information for DLQ behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100