Log ERROR instead of WARN of TimeToBeReceivedOnForwardedMessages is used

[timbussmann]

As the configurationsection will likely be removed completely without obsoletion attributes in v7 (as not supported by .net core), the idea was to increase the log severity with 6.3 to error in order to increase the likelihood of users noticing the log entry.

[danielmarbach]

Can we track that somehow so that we don't forget? Tim Bussmann <notifications@github.com> schrieb am Mo. 27. Feb. 2017 um 12:29:

…

As the configurationsection will likely be removed completely without obsoletion attributes in v7 (as not supported by .net core), the idea was to increase the log severity with 6.3 to error in order to increase the likelihood of users noticing the log entry. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4508>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKoslNtuNmKet6mSCwZKr1ShZAM86rBks5rgrOdgaJpZM4MM_pR> .

[WilliamBZA]

Milestone?

[danielmarbach]

@WilliamBZA yeah that is what we usually do. Was a hidden hint to create the milestone ;)

[timbussmann]

weird, I was pretty sure I added the milestone when I created the issue. Thanks @WilliamBZA

[timbussmann]

@Particular/nservicebus-maintainers any reason not to extend the scope of this issue to all configuration section warnings (see also #4644 (comment))?

[timbussmann]

closing this as #4644 has been merged and will be included in 6.3