Closed
Description
Steve Roy opened SPR-13267 and commented
The InvocableHandlerMethod logs request mapping values at the TRACE and more recently the DEBUG levels when a request can't be mapped without issue.
We normally run Spring at LOG.warn to keep the log chattiness down. We were a bit thrown off on the issue until the Spring logging was dropped to the TRACE level. We will have external partner systems calling us in Production and we can't run Production at even a DEBUG level to troubleshoot these problems.
This is going to be an ongoing issue for our software solution.
- steve
Affects: 4.1.6
Issue Links:
- Use higher log level in InvocableHandlerMethod.getMethodArgumentValues() [SPR-12925] #17518 Use higher log level in InvocableHandlerMethod.getMethodArgumentValues()
- 400 Bad Request for missing URI template variable is incorrect [SPR-13121] #17712 400 Bad Request for missing URI template variable is incorrect
- Improve warn logging in AbstractHandlerExceptionResolver [SPR-14392] #18965 Improve warn logging in AbstractHandlerExceptionResolver