Skip to content

Commit

Permalink
system: Don't log stack-trace on fatal JVM error
Browse files Browse the repository at this point in the history
Motivation:

Currently, dCache logs a stack-trace if there is a VirtualMachineError.
This is unnecessary as dCache was (presumably) working fine until Java
discovered a problem.

Modification:

Log the Error's toString output.

Result:

dCache no longer logs a stack-trace if there is a critical JVM error.

Target: master
Request: 3.2
Request: 3.1
Request: 3.0
Request: 2.16
Require-notes: yes
Require-book: no
Acked-by: Alert Rossi
Patch: https://rb.dcache.org/r/10603/
  • Loading branch information
paulmillar committed Oct 30, 2017
1 parent af0a7cd commit bb14aa3
Showing 1 changed file with 1 addition and 1 deletion.
Expand Up @@ -349,7 +349,7 @@ public void uncaughtException(Thread t, Throwable e)
_log.error(AlarmMarkerFactory.getMarker(PredefinedAlarm.FATAL_JVM_ERROR,
getCellDomainName(),
getCellName()),
"Restarting due to fatal JVM error", e);
"Restarting due to fatal JVM error: {}", e.toString());
return;
}

Expand Down

0 comments on commit bb14aa3

Please sign in to comment.