+

Passing Additional Arguments to the JVM to Control Mule

Standard Support for Mule 4.1 ended on November 2, 2020, and this version of Mule will reach its End of Life on November 2, 2022, when Extended Support ends.

Deployments of new applications to CloudHub that use this version of Mule are no longer allowed. Only in-place updates to applications are permitted.

MuleSoft recommends that you upgrade to the latest version of Mule 4 that is in Standard Support so that your applications run with the latest fixes and security enhancements.

If you want to pass additional arguments to the JVM that runs Mule, you can add wrapper.java.additional.n entries to the wrapper.conf file in the ${MULE_HOME}/conf directory, or you can pass the arguments at the command line by adding the -M switch.

For example, to set Mule’s encoding:

  • Add wrapper.java.additional.1=-Dmule.encoding=ISO-8859-1 to the Wrapper configuration file, or you could add -M-Dmule.encoding=ISO-8859-1 to the Mule script at the command line.

If you add wrapper.java.additional.n entries to the configuration file, you must change each instance of n to a consecutive number, or Java does not parse the properties correctly.

You can set Java Service Wrapper properties in the wrapper that you implement.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub