Author: Artemiy Degtyarev
Imagine you are deploying an open source Java application in Docker. You pull the image, run it, and before the first
log line appears, the JVM dies with this:
# A fatal error has been detected by the Java Runtime Environment: # # SIGILL (0x4) at pc=..., pid=1, tid=... # # Problematic frame: # v ~AdapterBlob
Enter fullscreen mode
Exit fullscreen mode
That is exactly what happened to some users of Axelix when they started Axelix
Master. SIGILL means illegal instruction : the CPU was asked to execute an instruction it does not support. That is
not something you expect from a Java application. Java is supposed to be "write once, run anywhere", and bytecode does not
contain CPU instructions.
We investigated it, fixed it, and wrote this article about it. It is a good story about a new JVM feature, the AOT
cache, and a small detail of its design that turned out to matter a lot for anyone who ships a pre-built Docker image.
What we saw
The bug was reported as #1744 .β¦