(Java) Ftp2 Debug Log File Path

Demonstrates how to use the DebugLogFilePath property to get information if a Chilkat method crashes or hangs.

Chilkat Java Downloads Java Libs for Windows, MacOS, Linux, Alpine Linux Java Libs for Android

import com.chilkatsoft.*;

public class ChilkatExample {

  static {
    try {
        System.loadLibrary("chilkat");
    } catch (UnsatisfiedLinkError e) {
      System.err.println("Native code library failed to load.\n" + e);
      System.exit(1);
    }
  }

  public static void main(String argv[])
  {
    CkFtp2 ftp = new CkFtp2();

    // ...
    // ...

    // Insert this code just before the method call that crashes or hangs.
    ftp.put_VerboseLogging(true);
    ftp.put_DebugLogFilePath("/some/file/path/sftp_debug_log.txt");

    // Make the call that crashes or hangs,
    // for example, if the method is PutFile:

    String remoteFilePath = "...";
    String localFilePath = "...";
    boolean success = ftp.PutFile(localFilePath,remoteFilePath);

    // Note: If the method returns control to your application code, then it did not crash within Chilkat.
    // The DebugLogFilePath property causes all information that would be recorded in the LastErrorText to be emitted to the
    // log file (with immediate file write flushing, i.e. no buffering).  Thus, in a crash situation,
    // the log file will contain information up to the point of the crash.

    if (success == false) {
        System.out.println(ftp.lastErrorText());
        return;
        }
  }
}