Skip to content

Documentation Enhancement: clarify the case which "error-channel" works #3024

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tonny1983 opened this issue Aug 9, 2019 · 0 comments · Fixed by #3037
Closed

Documentation Enhancement: clarify the case which "error-channel" works #3024

tonny1983 opened this issue Aug 9, 2019 · 0 comments · Fixed by #3037
Assignees
Milestone

Comments

@tonny1983
Copy link

Considering the following two cases:
Case 1: An exception is thrown in the caller's thread (synchronous processes);
Case 2: An exception is thrown in a latter thread after the caller puts a message (asynchronous processes)

In Case 1, the exception will be thrown to the caller. Meanwhile In Case 2, the caller's thread will return immediately when it puts the message, and therefore it never knows what will happen further. So, the message will be routed to the default errorChannel or the channel defined by the errorChannel value in the message's header only in the case.

It is a little confusing that the document does not clarify the condition and there have been already many related questions.

@garyrussell garyrussell added this to the 5.2.RC1 milestone Aug 9, 2019
@garyrussell garyrussell changed the title Documentation Enhancemen: clarify the case which "error-channel" works Documentation Enhancement: clarify the case which "error-channel" works Aug 9, 2019
@artembilan artembilan self-assigned this Aug 19, 2019
artembilan added a commit to artembilan/spring-integration that referenced this issue Aug 19, 2019
Fixes spring-projects#3024

To avoid confusing about `errorChannel` header behavior and make it more
clear how to handle errors in Spring Integration flows, it would be
better to present an `Error Handling` chapter on the top level.
So, now it is a first chapter of the `Appendices` section
garyrussell pushed a commit that referenced this issue Aug 19, 2019
Fixes #3024

To avoid confusing about `errorChannel` header behavior and make it more
clear how to handle errors in Spring Integration flows, it would be
better to present an `Error Handling` chapter on the top level.
So, now it is a first chapter of the `Appendices` section
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants