Stack trace for uncaught exception?
Christopher Bongaarts
cab at umn.edu
Fri Jan 15 21:45:04 UTC 2021
On 12/28/2020 12:29 PM, Cantor, Scott wrote:
>
> Is there a way to get the stack trace logged when an uncaught exception occurs?
> Well, I would have thought that it was simply passing the underlying exception to logback. The code is supposed to do that, and then it would be up to the stack trace setting in the logback format string, which we have set to full I think.
>
Just to close the loop on this - we had our logback.xml set to log
"short" stack traces to idp-process.log and "full" traces to
idp-warn.log, so I was able to see this more fully (and confirmed that
Rod's issue/fix should cover it - thanks!!).
I also encouraged my colleague who reported the problem to file a bug
with 4D now that we know exactly what it is sending and not supposed to :)
--
%% Christopher A. Bongaarts %% cab at umn.edu %%
%% OIT - Identity Management %% http://umn.edu/~cab %%
%% University of Minnesota %% +1 (612) 625-1809 %%
More information about the users
mailing list