Log caught exception in MappingJackson2HttpMessageConverter [SPR-11403]

[spring-projects-issues]

Oliver Drotbohm opened SPR-11403 and commented

#15886 introduced more detailed log output for MappingJackson2HttpMessageConverter in case of an invalid mapping configuration. However, the log output only states "Failed to evaluate deserialization for type: Foo" which is not too helpful, as you don't find out about the details of the invalid mapping of said class.

It would be helpful to also log the cause as it contains detailed information about what actually is misconfigured.

---

Affects: 4.0.1

Issue Links:

• Poor jackson parsing error message in MappingJackson2HttpMessageConverter [SPR-11603] #16226 Poor jackson parsing error message in MappingJackson2HttpMessageConverter
• MappingJackson2(Http)MessageConverter should be more verbose in canRead/canWrite checks (on Jackson 2.3) [SPR-11261] #15886 MappingJackson2(Http)MessageConverter should be more verbose in canRead/canWrite checks (on Jackson 2.3)
• MappingJackson2HttpMessageConverter should not always log a warning [SPR-14163] #18735 MappingJackson2HttpMessageConverter should not always log a warning

1 votes, 3 watchers

[spring-projects-issues]

Johannes Hiemer commented

I need to agree here. Switching to 4.0.1 made it a lot easier to debug at all, but it would be very nice if one could see the the log which is visible when stepping into the canRead implementation.

[spring-projects-issues]

Juergen Hoeller commented

Seems we simply missed to log the cause there! That's indeed a bug...

Juergen

[spring-projects-issues]

Juergen Hoeller commented

Fixed through appending the toString'ed exception at the existing warn level message, and logging the full stacktrace in case of debug level being enabled.

Juergen

[spring-projects-issues]

Johannes Hiemer commented

Thanks a lot for the quick response! :-)