Closed rizaumami closed 2 years ago
That seems to be a misconfigured JVM (probably the server, not the desktop java edition), not a bug in Raccoon.
@onyxbits I disagree. This bug is caused here: https://github.com/onyxbits/raccoon4/blob/master/src/main/java/de/onyxbits/weave/diag/ReportManager.java#L109
if e.getMessage()
returns null (which happens on certain exceptions) this bug happens as report.setFingerprint
is never called. Therefore this is a problem of bad error handling of Raccoon.
That's just a detour. The basal bug happens somewhere between the Locale and Currency class (Currency getting an invalid Locale). This should not normally happen. At least not with a desktop Java edition. AFAIR, Debian offers a server edition which is basically a stripped down variant. So my guess here is missing config files.
Your guess may be correct, it is difficult to know what the original exception was if the exception handling code fails and raises an exception on it's own...
In my opinion an exception handling code should be safe in all cases. Therefore I would recommend to add an report.setFingerprint(new BigInteger.ZERO);
in the empty exception handler https://github.com/onyxbits/raccoon4/blob/master/src/main/java/de/onyxbits/weave/diag/ReportManager.java#L113 or alternatively add a null
check every where getFingerprint()
is called.
Using
openjdk-11-jre
:Using
openjdk-18-jre
: