Assertion failed: exClass != NULL at /home/meganwoods/cw/bc/bc-lts-java/native_c/jniutil/exceptions.c:40

[Monsterovich]

This error occurred unexpectedly after Lanemu (a GraalVM-built image) had been running for a day.

Here's how I build this image:
https://gitlab.com/Monsterovich/lanemu/-/blob/main/.gitlab-ci.yml?ref_type=heads#L74-85

The Lanemu startup command:

Lanemu-headless -Xmx150m --headless --access=access_proxy.dat --name=Suplib --port=10001 --udp --rudp --vpn.ip=10.55.0.1 --vpn.mask=255.255.0.0

I don't know if this is a bug in GraalVM or Bouncy Castle, but the stack trace seems to point to native code? Maybe I built the image incorrectly somehow? Although it worked fine for a whole day.

[mwcw]

Ok I know very little about Graal VM so I ended up pointing the machine (Claude) at this issue.

It reports that the issue should be fixed in your commit 15d332f1

 Short version: this is the GraalVM JNI registration, not a fault in GraalVM or in the Bouncy Castle crypto. You have already fixed it yourself.

What happened

  Our native code raises Java exceptions by calling JNI FindClass with a class name. In a GraalVM native image, FindClass only resolves classes that you have registered for JNI. Being reachable
  in the image is not enough. The JNI lookup table is separate.

  At the time you built the failing binary, misc/graalvm-jni-config.json registered only org.p2pvpn.tuntap.TunTapLinux. So FindClass for org.bouncycastle.crypto.InvalidCipherTextException
  returned NULL. Our code then aborted the process at exceptions.c:40.

  Your commit 15d332f1, "Added more entries for GraalVM", adds all six exception classes. That is the correct fix. If you rebuild from that commit or later, this abort will not recur.

  Why it ran fine for a whole day

  Those six code paths are all error paths. A healthy session never touches them. The path you hit runs when an AEAD tag check fails, so it needs a corrupt, forged, or replayed packet. Your
  first such packet arrived about a day in. That was the first time the code ever ran in that process. Nothing degraded over the day.

  Two more classes to add

  Our native code looks up eight classes in total. Your config now covers six. Please also add these two, which the CPU variant and feature reporting code uses:

  { "name": "java.lang.String" },
  { "name": "java.lang.String[]" }

Can you confirm the Bouncy Castle LTS version?

MW