Tag Archives: Mule ESB

You all must be knowing that Mule ESB 3.8 by default supports only TLSV1.1 and TLSV1.2. Some applications need to post to endpoints that are based on TLSV1.0 and in order for it to work in local while developing your application, you might have to enable TLSV1.0 in Anypoint Studio.

Follow the steps to enable TLSV1.0 so that your applications running through Anypoint Studio will not complain any errors:

Go to the AnyPoint Installation folder.

Navigate to “Plugins” directory if you are using Windows.

If you are using Mac, then navigate to Applications –> Anypoint Studio –>Contents –> Eclipse–>plugins.

Now search for folder “org.mule.tooling.server.3.8.x.ee_6.1.x.yyy.mm.dd” and then navigate to directory “mule” and then to “conf” folder.

Now you should find a files with name “tls-default.conf” and “tls-fips140-2.conf”.

Edit each of the file by opening it and search for “enabledProtocols”.

You should see “enabledProtocols=TLSv1.1,TLSv1.2”.

Now add TLSv1 to the enabledProtocols.

It should look like “enabledProtocols=TLSv1,TLSv1.1,TLSv1.2”.

Now restart your Anypoint Studio just to make sure that it picks up the new settings and your apps now should be supporting TLS1.0 with settings.

Similarly if you need to disable TLSv1.0 as it is not accepted by PCi compliance, remove it from the enabledProtocols.

Note: This feature of editing the TLS values is available since Studio 5.4.3 as per the MuleSoft website. I hope this helps!!!

In the previous post I have explained on how to fix the “bind exception” that occurred because we are trying to run an application on the same port that other application is running and advised to move the configuration section for listeners/requests to Domain project if the other application is also a Mule application.

After moving the configuration section for listeners/requests to a Domain project and when everything was running fine, one bad day you see the following exception:

RROR 2016-09-0522:33:10,371[main] org.mule.module.launcher.DefaultArchiveDeployer:+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Failed to deploy artifact 'anotherapp', see below +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
org.mule.module.launcher.DeploymentInitException:NoSuchBeanDefinitionException: No bean named 'HTTP_Listener_Configuration' is defined
at org.mule.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:205)~[mule-module-launcher-3.8.0.jar:3.8.0]
at org.mule.module.launcher.artifact.ArtifactWrapper$2.execute(ArtifactWrapper.java:63)~[mule-module-launcher-3.8.0.jar:3.8.0]
at org.mule.module.launcher.artifact.ArtifactWrapper.executeWithinArtifactClassLoader(ArtifactWrapper.java:136)~[mule-module-launcher-3.8.0.jar:3.8.0]

If you ever see the exception saying “No bean named ‘HTTP_Listener_Configuration’ is defined” and if http configuration is defined the Domain project, first do not blame your application. It is not your application’s fault. You may have to verify if the Domain project is deployed or not. If it is not deployed, then the culprit is the Domain project.

Action: Since the error is related to HTTP Listener, check if any other application is running on the same port that the listener is configured to run. Sort out the issue either by stopping the other application or changing the port in the listener configuration.