Uploaded image for project: 'YADE - Yet Another Data Exchange Tool'
  1. YADE - Yet Another Data Exchange Tool
  2. YADE-209

YADE shall raise a specific exception if an invalid protocol type is used

    XMLWordPrintable

Details

    • Feature
    • Status: Released (View Workflow)
    • Minor
    • Resolution: Fixed
    • 1.7.1
    • 1.9
    • YADE Client
    • None

    Description

      • Current Situation
        • When user mistypes or configures an invalid transfer protocol, then YADE will raise an unrelated error. In this case the user has misspelled the protocol "SFTP" to "STFP":
        • Please see the error message and attached job:
           
          2014-08-28 11:14:59.411+0200 [debug]  passive_mode = 
          2014-08-28 11:14:59.411+0200 [debug]  port = 22
          2014-08-28 11:14:59.411+0200 [debug]  protocol = stfp
          2014-08-28 11:14:59.411+0200 [debug]  target_transfer_mode =  
          2014-08-28 11:14:59.411+0200 [debug]  user = 
          2014-08-28 11:14:59.411+0200 [debug]  password = *****
          2014-08-28 11:14:59.411+0200 [debug]  ssh_auth_method = password
          2014-08-28 11:14:59.411+0200 [debug]   
          2014-08-28 11:14:59.419+0200 [debug]  DEBUG [main] (SOSVfsConnectionFactory.java:54) - create connection pool 
          2014-08-28 11:14:59.420+0200 [debug]  DEBUG [main] (SOSFTPOptions.java:1063) - SOSVfs_D_199: DataSourceType = local 
          2014-08-28 11:14:59.424+0200 [debug]  TRACE [main] (VFSFactory.java:211) - SOSVfs_D_0201: VFSFactory::getHandler returns instance of class com.sos.VirtualFileSystem.local.SOSVfsLocal 
          2014-08-28 11:14:59.425+0200 [debug]  DEBUG [main] (SOSFTPOptions.java:947) - prefix_host = sos-paris.com 
          2014-08-28 11:14:59.426+0200 [debug]  DEBUG [main] (SOSFTPOptions.java:941) - SOSVfs_D_262: DataTargetType = stfp 
          2014-08-28 11:14:59.427+0200 [info]    INFO [main] (SOSDataExchangeEngine.java:984) - SOSJADE_E_0101: data transfer ended with error 'java.lang.Exception cannot be cast to java.lang.RuntimeException' 
          2014-08-28 11:14:59.429+0200 [info]    INFO [main] (SOSDataExchangeEngine.java:304) - Elapsed time = 140, per File = 140, total bytes = 0 
          2014-08-28 11:14:59.433+0200 [info]    INFO [main] (SOSDataExchangeEngine.java:314) - 
          2014-08-28 11:14:59.433+0200 [info]   ************************************************************************* 
          2014-08-28 11:14:59.433+0200 [info]    execution status     = failure. Errors reported. 
          2014-08-28 11:14:59.433+0200 [info]    successful transfers = 0 
          2014-08-28 11:14:59.433+0200 [info]    failed transfers     = 0 
          2014-08-28 11:14:59.433+0200 [info]    last error           = java.lang.Exception cannot be cast to java.lang.RuntimeException (java.lang.Exception cannot be cast to java.lang.RuntimeException) 
          2014-08-28 11:14:59.433+0200 [info]   *************************************************************************
          2014-08-28 11:14:59.433+0200 [info]    
          2014-08-28 11:14:59.435+0200 [ERROR]  ERROR [main] (SOSDExJSAdapterClass.java:74) - SOSDExJSAdapterClass ended abnormal. 
          2014-08-28 11:14:59.436+0200 [ERROR]  ERROR [main] (SOSDExJSAdapterClass.java:75) - java.lang.Exception cannot be cast to java.lang.RuntimeException
          2014-08-28 11:14:59.436+0200 [ERROR]  com.sos.DataExchange.SOSDataExchangeEngine.Execute(SOSDataExchangeEngine.java:295)
          2014-08-28 11:14:59.436+0200 [ERROR]  sos.scheduler.job.SOSDExJSAdapterClass.doProcessing(SOSDExJSAdapterClass.java:115)
          2014-08-28 11:14:59.436+0200 [ERROR]  sos.scheduler.job.SOSDExJSAdapterClass.spooler_process(SOSDExJSAdapterClass.java:70)
          2014-08-28 11:14:59.436+0200 [ERROR]   
          2014-08-28 11:14:59.440+0200 [info]   java.lang.ClassCastException: java.lang.Exception cannot be cast to java.lang.RuntimeException 
          2014-08-28 11:14:59.440+0200 [info]   	at com.sos.VirtualFileSystem.DataElements.SOSVfsConnectionFactory.getVfsHandler(SOSVfsConnectionFactory.java:103) 
          2014-08-28 11:14:59.440+0200 [info]   	at com.sos.VirtualFileSystem.DataElements.SOSVfsConnectionFactory.createConnectionPool(SOSVfsConnectionFactory.java:61) 
          2014-08-28 11:14:59.440+0200 [info]   	at com.sos.VirtualFileSystem.DataElements.SOSVfsConnectionFactory.<init>(SOSVfsConnectionFactory.java:32) 
          2014-08-28 11:14:59.440+0200 [info]   	at com.sos.DataExchange.SOSDataExchangeEngine.transfer(SOSDataExchangeEngine.java:848) 
          2014-08-28 11:14:59.440+0200 [info]   	at com.sos.DataExchange.SOSDataExchangeEngine.Execute(SOSDataExchangeEngine.java:292) 
          2014-08-28 11:14:59.440+0200 [info]   	at sos.scheduler.job.SOSDExJSAdapterClass.doProcessing(SOSDExJSAdapterClass.java:115) 
          2014-08-28 11:14:59.440+0200 [info]   	at sos.scheduler.job.SOSDExJSAdapterClass.spooler_process(SOSDExJSAdapterClass.java:70) 
          2014-08-28 11:14:59.440+0200 [info]   com.sos.JSHelper.Exceptions.JobSchedulerException: java.lang.Exception cannot be cast to java.lang.RuntimeException 
          2014-08-28 11:14:59.440+0200 [info]   	at com.sos.DataExchange.SOSDataExchangeEngine.Execute(SOSDataExchangeEngine.java:295) 
          2014-08-28 11:14:59.440+0200 [info]   	at sos.scheduler.job.SOSDExJSAdapterClass.doProcessing(SOSDExJSAdapterClass.java:115) 
          2014-08-28 11:14:59.440+0200 [info]   	at sos.scheduler.job.SOSDExJSAdapterClass.spooler_process(SOSDExJSAdapterClass.java:70)
          2014-08-28 11:14:59.441+0200 [ERROR]  COM-80020009  Une exception s92est produite. [step] [] [Z-JAVA-105  Java exception com.sos.JSHelper.Exceptions.JobSchedulerException: java.lang.Exception cannot be cast to java.lang.RuntimeException, method=spooler_process()Z [], in Remote_module_instance_server::step], method=call
          2014-08-28 11:14:59.443+0200 [info]   Job MySQL dump/FTP send terminated.
          2014-08-28 11:14:59.488+0200 [WARN]   SCHEDULER-280  Process terminated with exit code 1 (0x1)
          2014-08-28 11:14:59.981+0200 [WARN]   SCHEDULER-320  Could not send mail
          
      • Desired Behaviour
        • YADE should have presented an error message i.e. "invalid protocol" to the user that clearly explains what has been misconfigured.

      Attachments

        1. FTP send.job.xml
          0.8 kB
          Mahendra Patidar

        Issue Links

          Activity

            People

              oh Oliver Haufe
              mp Mahendra Patidar
              Mahendra Patidar Mahendra Patidar
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 4 hours
                  4h
                  Remaining:
                  Remaining Estimate - 4 hours
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified