Nav
You are viewing an older version of this section. Click here to navigate to the latest version.

Troubleshooting and Next Steps

Troubleshooting Ports

The Mule HA Demo Bundle uses the following ports on your local drive:

  • 7777 for Mule server 1

  • 7778 for Mule server 2

  • 8585 for the Mule Management Console

  • 8080 and 61616 for the WidgetUI Web app

If you currently use one or more of these ports for other purposes, you can change the ports that the WidgetUI Web app and Mule servers use.

Change the WidgetUI Port

In your Terminal or Console, execute the following script in the cluster/widgetUI folder:
play run --http.port=YOUR_CUSTOM_PORT
For example, execute play run --http.port=8090

Change the Servers’ Ports

In your Terminal or Console, execute a startServer script with the following system property:
startServer1 -M-Dmule.mmc.bind.port=YOUR_CUSTOM_PORT
For example, execute startServer1 -M-Dmule.mmc.bind.port=7779

Troubleshooting WidgetUI

If the Time to Complete Processing of Widget pane is not rendering correctly, refresh the Web browser page.

Next Steps

Explore our documentation to learn more more about Mule clustering and high availability.

  • Download a trial of Mule with the Mule Management Console to experiment with High Availability. (Download Runtime - Mule ESB Enterprise (with Management Tools).)

  • Install an Enterprise License to begin using the Mule Management Console to manage clusters in production.

  • For more information about Mule high availability, consult the Mule High Availability documentation.

  • For more information about Mule clustering, consult the Mule HA Clustering documentation.

  • For more information on managing Mule clusters, consult the Managing HA Clusters documentation.

  • For more information on managing Mule clusters using REST APIs, consult the REST API Reference documentation.

  • For more information on creating or disbanding clusters, consult Creating or Disbanding a Cluster documentation.