Project

General

Profile

Bug #839

logAndThrowException with null for briefMsg causes unexpected exception

Added by Mike Stults over 5 years ago. Updated about 4 years ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
Start date:
10/18/2016
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

when a caller passes in null for briefMsg, this causes a generic http code 500 from Tomcat. Check for null and set some default message so that a standard FDSN error report is provided and prevent the unexpected 500.

History

#1 Updated by Mike Stults about 5 years ago

  • Resolution set to Fixed

git commit m "issue 839, when briefMsg is null, reassign a new message and continue"
[master e6756db]
4 files changed, 83 insertions(+), 5 deletions(-)

#2 Updated by Mike Stults about 4 years ago

  • Target version set to 2.4

Also available in: Atom PDF