How to Collect SSL Debug Logs for Anypoint Studio Connectivity Issues

Note: these steps were executed and validated on Anypoint Studio 7.8.0, or newer versions.

A. If Studio is running on macOS:

1. Copy the below command into a text editor: 

   java -jar -XstartOnFirstThread -Djavax.net.debug=all /Applications/AnypointStudio.app/Contents/Eclipse/plugins/org.eclipse.equinox.launcher_1.5.700.v20200207-2156.jar --launcher.ini=/Applications/AnypointStudio.app/Contents/Eclipse --launcher.suppressErrors > /Users/minniemouse/Downloads/studioConsoleOutput.log 2>&1

2. In the command, edit the path below and confirm it is using the right JAR file. To check, go to Finder -> Applications -> Anypoint Studio App -> Right click on the App and select -> Show Package Contents -> Contents -> Eclipse -> Plugins -> sort alphabetically and search for "org.eclipse.equinox.launcher_********.jar":

   Examples:
   Studio 7.8.0: /Applications/AnypointStudio.app/Contents/Eclipse/plugins/org.eclipse.equinox.launcher_1.5.700.v20200207-2156.jar
   Studio 7.9.0: /Applications/AnypointStudio.app/Contents/Eclipse/plugins/org.eclipse.equinox.launcher_1.6.0.v20200915-1508.jar
   

3. Edit the path where the logs will be written:

   /Users/minniemouse/Downloads/studioConsoleOutput.log 2>&1

4. Open the Anypoint Studio INI file (refer to How to find the AnypointStudio ini file for more information) and locate the JDK used to open Studio. Open a terminal and Navigate to the JDK /bin folder before executing the command in the next step. This will ensure the JAVA version used for SSL Debug is the same as the one used when Studio is normally opened. 

   Example: 
   If the INI file shows /Applications/AnypointStudio.app/Contents/Eclipse/plugins/org.mule.tooling.jdk.macosx.x86_64_1.1.1/Contents/Home/bin/java
   then navigate to /Applications/AnypointStudio.app/Contents/Eclipse/plugins/org.mule.tooling.jdk.macosx.x86_64_1.1.1/Contents/Home/bin in the terminal

5. In the terminal, copy/paste the edited command and hit enter.
    
6. Studio should open -> Select a workspace -> Click "Launch".
    
7. Reproduce the issue.
    
8. Find the logs in the location defined in step 3. and either analyse the errors and/or attach the complete log output to a Support case for review.
    

B. If Studio is running on Windows:

1. Copy the below command into a text editor: 

   java -Djavax.net.debug=all -jar C:\AnypointStudio-7.10.0-win64\plugins\org.eclipse.equinox.launcher_1.6.100.v20201223-0822.jar --launcher.ini=C:\AnypointStudio-7.10.0-win64 --launcher.suppressErrors > C:\Users\username\AnypointStudio\studio-workspace\studioConsoleOutput.log 2>&1
   

2. In the command, edit the path below and confirm it is using the right JAR file. To check, go to Finder -> Applications -> Anypoint Studio App -> Right click on the App and select -> Show Package Contents -> Contents -> Eclipse -> Plugins -> sort alphabetically and search for "org.eclipse.equinox.launcher_********.jar":

   Example:
   Studio 7.10.0: C:\AnypointStudio-7.10.0-win64\plugins\org.eclipse.equinox.launcher_1.6.100.v20201223-0822.jar
   

3. Edit the path where the logs will be written:

   C:\Users\username\AnypointStudio\studio-workspace\studioConsoleOutput.log 2>&1

4. Open the Anypoint Studio INI file (refer to How to find the AnypointStudio ini file for more information) and locate the JDK used to open Studio. Open a terminal and Navigate to the JDK /bin folder before executing the command in the next step. This will ensure the JAVA version used for SSL Debug is the same as the one used when Studio is normally opened. 

   Example: 
   If the INI file shows C:\AnypointStudio-7.10.0-win64\plugins\org.mule.tooling.jdk.win32.x86_64_1.1.1\bin\javaw.exe 
   then navigate to C:\AnypointStudio-7.10.0-win64\plugins\org.mule.tooling.jdk.win32.x86_64_1.1.1\bin in the terminal

5. In the terminal, copy/paste the edited command and hit enter.
    
6. Studio should open -> select a workspace -> click "Launch".
    
7. Reproduce the issue.
    
8. Find the logs in the location defined in step 3. and either analyse the errors and/or attach the complete log output to a Support case for review.