Troubleshoot FTPS Connector - Mule 4

To troubleshoot Anypoint Connector for FTPs (FTPS Connector), become familiar with the information about troubleshooting Mule application issues.

Troubleshoot Mule Application Issues

Sometimes you are not sure why the application is failing and you require a better understanding of what is going on in the app’s interaction with the FTPS server.

To resolve this error:

  • Use the configuration file to increase the logging level on the server side.

  • Try to replicate the issue using an FTPS client, for example, Cyberduck or Filezilla. If the issue also occurs with these clients, then it is likely that the issue is not related to the Mule app.

  • Get better and more detailed logs on the Mule app side by enabling verbose logging for FTPS Connector and for the JSCH driver:

    1. Access Anypoint Studio and navigate to the Package Explorer view.

    2. Open your application’s project name.

    3. Open the src/main/resources path folder.

    4. Open the log4j2.xml file inside the folder.

    5. If the following line is already in the log4j2.xml file, uncomment it to enable it; otherwise, add it:

        <AsyncLogger name=“org.mule.extension.ftp” level=“TRACE”/>
        <AsyncLogger name=“org.apache.commons.net” level=“DEBUG”/>
    6. Add the following argument to your run configuration:

      `-M-Djavax.net.debug=ssl,handshake`
  • Try to minimize or remove unnecessary DataWeave data transformations (you could even use hard coded data) to minimize the app’s complexity and determine whether the issue is with the interaction between the app and the FTPS server.

For additional information about enabling verbose logging for SDK components in your Mule application, see the troubleshoot SDK components documentation.