Loading

Hybrid Standalone Mule Server Remains in "Connected" Status and Never Transitions to "Running" in Anypoint Runtime Manager

Udgivelsesdato: Jun 10, 2026
Beskrivelse

A Hybrid Standalone Mule server registered in Anypoint Runtime Manager (ARM) remains stuck in "Connected" status and never transitions to "Running". This article explains a specific symptom and cause.

For general guidance and meaning of server statuses such as "Connected" and "Running", refer to Reference [1].
If you have an application stuck in "Starting" or "Stopping" state, refer to Reference [2].

Symptom

In this issue, the MuleSoft Mule runtime exhibits the following behavior:

  • Mule runtime starts and domains deploy without errors. All applications appear to start normally.
  • No specific error is seen in mule_agent.log
  • Running df -h shows 100% disk usage on one or more directories.
  • In mule_ee.log, the following warning and error may appear:
WARN  2026-06-08 12:49:44,591 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.plugin.manager.MulePluginManager: Cannot start plugin 'mule-agent-plugin'. Plugin will be unregistered
...
Caused by: java.lang.ExceptionInInitializerError: Exception java.lang.UnsatisfiedLinkError: Failed to create temporary file for /com/sun/jna/linux-x86-64/libjnidispatch.so library: No space left on device [in thread "WrapperListener_start_runner"]

Cause

This issue in MuleSoft Hybrid Standalone deployments is caused by insufficient free disk space on the server. When disk space is exhausted, the JVM is unable to extract the JNA native library (libjnidispatch.so) to a temporary file. As a result, the mule-agent-plugin fails to start and is unregistered, preventing the server from transitioning from "Connected" to "Running" in Anypoint Runtime Manager.

Løsning

To resolve the issue where a MuleSoft Hybrid Standalone Mule server is stuck in "Connected" status due to insufficient disk space, follow the steps below:

  1. Run df -h on the on-premise server to check disk usage across all mount points.
  2. Identify and free up disk space on any directory showing 100% usage.
  3. Once sufficient disk space is available, restart the Mule runtime.

NOTE:

  • This issue can occur even if /tmp is not at 100% usage. For example, 100% usage of /home or other directories can also be a cause. Free up any location that shows 100% disk usage.
  • The system properties jna.tempdir and java.io.tmpdir determine the location where the JNA temporary file is written.

 

Reference

[1] What is the Difference Between "Running" and "Connected" Server Status with MuleSoft Runtime Manager
[2] How to Delete a Hung Application in Starting or Stopping State in ARM

Yderligere ressourcer

If the steps above did not resolve the issue, open a support case with the required information described in the article: What Information to Collect for Anypoint Runtime Manager case - Server Status category

Vidensartikelnummer

005386574

 
Indlæser
Salesforce Help | Article