Mr. Freedman is a seasoned architect and developer with over twenty years experience in the software industry. In the last ten years, he has focused on Java technologies and has led many successful projects, from web applications to Swing-based rich clients, back-end systems and large integration efforts. ! Richard is a DZone MVB and is not an employee of DZone and has posted 6 posts at DZone. You can read more from them at their website. View Full User Profile

Running Multiple Instances of Mule 3.0

  • submit to reddit

I’m working on some Mule services, with the new 3.0.1 version, and need to run multiple instances of Mule on the same physical server.

With Mule 2.x, this was done by running the provided script to copy some of the Mule directories, and then using the MULE_BASE environment variable to point to the new location.

With Mule 3.0, the script still exists, but deploying multiple instances in this manner does not work correctly.

After some experimentation, what worked for me was to copy the entire Mule installation directory, and set the MULE_HOME environment variable for each new instance.


Your rating: None
Published at DZone with permission of Richard Freedman, author and DZone MVB.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)



Aravind Yarram replied on Wed, 2011/01/05 - 9:26am

good but surprised people are still using mule

Andrew Perepelytsya replied on Wed, 2011/01/05 - 1:14pm

Aravind, not sure what you mean by your comment. People are using Mule and the number of users is growing.

Now, back to the article (is it an article at all? I leave it up to the editors...). MULE_BASE isn't supported in Mule 3, it is a more complex environment with multiple applications running in the same JVM. Mule 3.1.x dropped the script you mentioned altogether. As well as a requiremet to set MULE_HOME.

Thus, it becomes as easy as taking a zip/tar.gz, unpacking as many copies as needed, then "cd bin; mule"

Enjoy :)


P.S.: I would expect this thread on a Mule user list, not sure why it appeared on JavaLobby.

Saddle Integration replied on Thu, 2011/01/06 - 7:49am

just visit saddle mule esb We proudly announce that Saddle goes Open source What is Saddle? Saddle is an Open Source NetBeans-based graphical frontend to configure the Mule ESB. It allows you to graphically create, view, or edit the configuration files of Mule v2.x and 3.x. You can even convert a v2.x configuration to a v3.x configuration. Furthermore, it enables you to graphically map messages from different systems and to apply Java buisiness logic with all comfort you are used from your Java IDE. Once the configuration work is done, Saddle allows you to administrate and monitor your runing Mule instances via any web browser. This also includes the graphical tracing of messages through your integration schema. Learn more about the features of Saddle in the documentation section.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.