JDK
Requirements and Limitations for Hybrid Standalone Instances
Plan and configure your hybrid standalone infrastructure by understanding the licensing requirements, infrastructure specifications, and operational limitations that govern hybrid standalone deployments.
MuleSoft License Compliance
You are responsible for ensuring compliance with your MuleSoft licensing for hybrid standalone deployments.
Licensing is based on the maximum allocated cores consumed by your Mule runtime instances:
-
Core calculation is based on logical or allocated cores available to the Mule instance or server.
-
Allocated cores are configured through OS, VM, container, or Mule configuration settings.
-
Core count is determined by the number of cores visible to the Java Virtual Machine running Mule.
-
Physical cores are not considered in licensing; only logical or virtual cores as reported by the OS are counted.
-
Each VM or container instance is metered separately, even if multiple instances run on the same physical host.
-
Fractional cores are always rounded up to the nearest integer value.
If cores are not explicitly allocated to Mule, the number of logical or virtual cores available on the physical or virtual machine or container as informed by the OS determines the core count.
Requirements
Ensure your infrastructure meets the minimum specifications and configuration requirements for successful hybrid standalone deployment and operation.
Hardware Requirements
Minimum hardware specifications for Mule runtime engine on hybrid standalone instances:
-
2 GHz CPU or 1 virtual CPU in virtualized environments, 2+ cores recommended for production workloads.
-
1 GB RAM minimum (Mule runtime), 4GB RAM minimum recommended for hybrid deployments, 8GB+ recommended for production environments.
-
4 GB minimum (Mule runtime), 10GB+ available disk space recommended for applications and logs.
-
x86 and x64 architectures supported.
-
Reliable internet connectivity for Anypoint Platform communication.
| Adjust RAM allocation to match your latency requirements and the size and number of simultaneous messages that applications process. |
Software Requirements
Verify that you use a supported version of Java before installing Mule runtime engine:
| Software | Version |
|---|---|
JDK 17 |
| Though you can run a different JDK of choice, MuleSoft doesn’t support or take action to fix issues if they are traced back to the JDK. |
Supported Operating Systems
Mule is supported on any operating system that runs a Java Runtime Environment (JRE) from a supported JDK.
Mule runtime engine passed functional testing against these software and operating systems:
-
MacOS 10.15
-
HP-UX 11i V3
-
AIX 7.2
-
Windows Server 2019
-
Windows 10
-
Solaris 11.3
-
Red Hat Enterprise Linux 9.4
-
Ubuntu Server 20.04
-
Adoptium OpenJDK distribution
Limitations
Be aware of the constraints and limitations that affect hybrid standalone deployments to plan your infrastructure accordingly.
Infrastructure Scaling Limits
Design your server infrastructure within these hard limits to ensure scalable and manageable hybrid standalone deployments.
| Component | Hard Limit |
|---|---|
Maximum number of servers (not Runtime Fabric) |
500 |
Maximum number of servers per server group |
20 |
Maximum number of servers per cluster |
8 |
Network Configuration Requirements
Proper network configuration is essential for Runtime Manager agent connectivity and secure communication with Anypoint Platform services. Network allowlists, firewall rules, and port configurations must be properly configured to ensure reliable hybrid standalone operations.
For comprehensive network configuration guidance, refer to Adding Ports, IPs, and Hostnames for Runtime Manager Agent.



