Mule 3.8 supports only TLSv1.1 and TLSv1.2 by default due to vulnerability issues with TLSV1. So, by default only v1.1 and v1.2 TLS are enabled both at the Mule Runtime and the Anypoint Studio settings. This scenario is applicable when you have a https requestor in your flow and configure it to enable the TLSv1, as … Continue reading Resolve Error “Some selected protocols are invalid…”
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 … Continue reading Enabling/Disabling TLS settings in MuleSoft’s Anypoint Studio
Sometimes, you may see this error when you deploy your mule application in Mule Runtime and you might be wondering what could be the reason for the error. java.lang.NoClassDefFoundError: org/apache/http/config/Lookup at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) The reason is because org.apache.http.config.Lookup class is available in httpcore-4.3.jar and so you need to check if the runtime … Continue reading NoClassDefFoundError: org/apache/http/config/Lookup
This is one more issue if .NET client applications are trying to hit https endpoint in your Mule 3.8 application, they may get the following error: The request was aborted; could not create SSL/TLS secure channel The fix for this issue is to add the following statement: ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12 | SecurityProtocolType.Ssl3;
In the maven command while building your application add “-Dmaven.test.skip=true” and it will skip the unit tests. For example: mvn clean package -Dmaven.test.skip=true Hope this helps!