MuleSoft · Mule runtime

MULE:FATAL_JVM_ERROR

Short answer

MULE:FATAL_JVM_ERROR means a fatal error occurred in the JVM, such as a stack overflow. It cannot be handled in a flow, and the only safe recovery after a VirtualMachineError is to restart the Mule runtime instance.

VerifiedLast verified

01Error text

MuleSoft error
Error type: MULE:FATAL_JVM_ERROR

02Likely causes

  • A fatal error occurred, such as stack overflow.
  • Mule wraps the error as MULE:FATAL and raises a FATAL_ERROR_RAISED alert.
  • It is a CRITICAL error, and critical errors cannot be handled.

03How to fix it

  1. Restart the Mule runtime instance. The docs state this is the only safe recovery action after a VirtualMachineError.
  2. Search the logs for VirtualMachineError, OutOfMemoryError or StackOverflowError to find what led to it.
  3. Configure health checks and automatic restarts on managed deployment targets, and use a process supervisor on-premises.
  4. Fix the cause, for example unconsumed streams that hold resources and can lead to an OutOfMemoryError.

04Official documentation

Test every fix in a non-production environment before you apply it to production. See how entries are verified.

More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.