Stack trace for uncaught exception?
cab at umn.edu
Mon Dec 28 17:22:23 UTC 2020
We upgraded to IdP 4.0.1 (plus Jetty 9.4.31 and RHEL7-provided
openjdk-11) yesterday (extremely smooth overall thanks to good advice
from Scott and the team - thanks!!).
We are getting a small number of these:
2020-12-28 08:53:12,127 - 10.21.43.63 - ERROR
[net.shibboleth.idp.authn:-2] - Uncaught runtime exception
java.lang.IllegalArgumentException: range=en_us at
The errors in question are coming from the embedded browser in the 4D
database client (user agent:
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/72.0.3626.121 Safari/537.36"). Visiting the page in
"real" Safari (same useragent but with "Chrome/87.0.4280.88 ") does not
trigger the exception.
This was working on our previous IdP (3.3.0, Jetty 9.3.something,
RHEL7-provided Oracle JDK 8).
Unfortunately the error does not include a stack trace, and there's no
other log messages nearby to get an idea of where the problem is. From
the jetty access logs, I can confirm that the error is occurring
immediately on receipt of the initial SAML2 Redirect SSO request (which
returns an HTTP 500 error instead of redirecting to the Spring
"execution" flow URL as one would expect).
Is there a way to get the stack trace logged when an uncaught exception
%% Christopher A. Bongaarts %% cab at umn.edu %%
%% OIT - Identity Management %% http://umn.edu/~cab %%
%% University of Minnesota %% +1 (612) 625-1809 %%
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users