When using or planning to upgrade the Mule Runtime, it is often useful to be aware of any existing product issues that may be a concern with your implementation. This guide provides some details of approaches you can take when investigating upgrade options for the Mule Runtime.
Patches provided by MuleSoft Support typically follow the format SE-<ID>-<VERSION>.jar. These are generally applied in the lib/user directory, as per the article in: How to apply patches in Mule Runtime. Search for these patches using the format SE-<ID> within the Product Documentation, or a preferred search engine to see if these return relevant results in the Mule Product Release notes.
Note: Keep in mind that due to the nature of the product, some patches do not follow the same naming convention as detailed above. These will need to be manually checked. In some cases, these patches are newer versions of third-party libraries, and newer versions may already exist in the updated releases of the product. Checking the included libraries (for example in the lib directory) of the newer product can help with this.
Manually checking the release notes for the versions between your existing and current product, will help with determining any existing known product issues and also details of new product features and changes with the product.
You can search for known issues in both Mule and APIKit for the open source components of these Mule Products. This can be searched from: https://www.mulesoft.org/jira/. Advanced search options to filter on affected Versions and what version an issue has been fixed in, can be found in Jira's documentation.
It is possible to review the commit history for the Community Mule ESB product, for example, the recent changes for the 4.x version of the product are listed in: https://github.com/mulesoft/mule/commits/mule-4.x. Additionally, you can search for 'MULE-<ID>' issues discovered by searching the Community Jira for more information on any fixes. This does not incorporate Enterprise code changes, and may significantly differ from the Enterprise implementation.
001114965

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.