AbstractJackson2HttpMessageConverter incorrectly logs at WARN level after upgrading to Jackson 2.9 [SPR-16947]

[spring-projects-issues]

Mark Chesney opened SPR-16947 and commented

The verbiage of exception messages changed from "Can not find" to "Cannot find" in Jackson 2.9 with PR #1682

e.g.

WARN o.s.h.c.j.MappingJackson2HttpMessageConverter : Failed to evaluate Jackson deserialization for type [[collection type; class com.google.common.collect.ImmutableList...

---

Affects: 4.3.18, 5.0.7

Issue Links:

• MappingJackson2HttpMessageConverter should not always log a warning [SPR-14163] #18735 MappingJackson2HttpMessageConverter should not always log a warning

Referenced from: pull request #1859

Backported to: 4.3.19

[spring-projects-issues]

Juergen Hoeller commented

Good catch! I'll backport this to 5.0.8 and 4.3.19 ASAP.

[spring-projects-issues]

Juergen Hoeller commented

I've also adapted our analogous detection logic in org.springframework.messaging.converter.MappingJackson2MessageConverter accordingly (which currently is a duplicate of AbstractJackson2HttpMessageConverter.logWarningIfNecessary since there is no proper place to reuse it from).

[spring-projects-issues]

Juergen Hoeller commented

It turns out that we can simplify this to just a "Cannot find" check on Spring Framework 5.1 since we formally require Jackson 2.9+ now. In the backports, we'll have to check for both variants (even if we technically require Jackson 2.9+ in a few places for other reasons already).