Skip to content

Conversation

@artembilan
Copy link
Member

Fixes #3555

The default global errorChannel has a LoggingHandler as a subscriber. It is subscribed without any order which may lose logging messages, when another subscriber with re-throw is present.

  • Set default LoggingHandler on the default errorChannel to Ordered.LOWEST_PRECEDENCE - 100 to give a room for custom subscribers without an order and still get error logged

Fixes spring-projects#3555

The default global `errorChannel` has a `LoggingHandler` as a subscriber.
It is subscribed without any `order` which may lose logging messages,
when another subscriber with re-throw is present.

* Set default `LoggingHandler` on the default `errorChannel` to `Ordered.LOWEST_PRECEDENCE - 100`
to give a room for custom subscribers without an `order` and still get error logged
Co-authored-by: Gary Russell <grussell@vmware.com>
@garyrussell garyrussell merged commit 508fb16 into spring-projects:main Nov 16, 2022
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 this pull request may close these issues.

Reconsider a default order value for default LoggingHandler subscribed into a default errorChannel by the framework

2 participants