Bug #931
NO_CONTENT gets logged at ERROR level in log4j logs
Start date:
12/20/2017
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Description
When there's no data to send back, in the EndPoint I have:
return IrisProcessingResult.processError(Status.NO_CONTENT, "No Data Found");
In the logs, this shows up as:
2017-12-20 16:08:54,046 [http-bio-8080-exec-25] ERROR ServiceShellException - No Data Found detailed: null
This 'pollutes' the logs.
Should probably be logged as DEBUG or maybe INFO, but definitely not ERROR
History
#1 Updated by Mike Stults over 6 years ago
- Resolution set to Fixed
- Target version deleted (
2.4)
2018-05-16 0ab79b8 - change 204 or 404 exception log message level to INFO, was ERROR
#2 Updated by Mike Stults over 6 years ago
- Assignee set to Mike Stults
#3 Updated by Mike Stults over 6 years ago
- Target version set to 2.4.4
2018-05-25 5a3b275 (Mike Stults): (HEAD > master, tag: v2.4.4, origin/master, origin/HEAD) - v2.4.4 for issues 939, 931, 927, 894, 841
uploaded webserviceshell/2.4.4/webserviceshell-2.4.4.jar 8545 KB