Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-10812

Camel-FTP component does not set CamelFtpReplyCode in some case(ex 530)

XMLWordPrintable

    • % %
    • +
    • Hide
      • unzip attached project
      • mvn install
      • run the application on karaf (we don't need to setup any FTP server to reproduce the issue)
      • check the fuse.log 
        2019-06-11 10:03:05,702 | WARN  |  - timer://timerName | o.a.c.c.f.r.RemoteFileProducer   | 62 - org.apache.camel.camel-core - 2.21.0.fuse-730078-redhat-00001 | Writing file failed with: File operation failed: 530 Permission denied.
. Code: 530
2019-06-11 10:03:05,705 | INFO  |  - timer://timerName | reproducer                       | 226 - reproducer - 1.0.0.SNAPSHOT | ***** Check CamelFtpReplyCode in headers: {breadcrumbId=ID-****, CamelFileName=null, firedTime=Tue Jun 11 10:03:04 JST 2019}
      Show
      unzip attached project mvn install run the application on karaf (we don't need to setup any FTP server to reproduce the issue) check the fuse.log 2019-06-11 10:03:05,702 | WARN | - timer://timerName | o.a.c.c.f.r.RemoteFileProducer | 62 - org.apache.camel.camel-core - 2.21.0.fuse-730078-redhat-00001 | Writing file failed with: File operation failed: 530 Permission denied. . Code: 530 2019-06-11 10:03:05,705 | INFO | - timer://timerName | reproducer | 226 - reproducer - 1.0.0.SNAPSHOT | ***** Check CamelFtpReplyCode in headers: {breadcrumbId=ID-****, CamelFileName=null, firedTime=Tue Jun 11 10:03:04 JST 2019}
    • Fuse 7.6 - Sprint 55 (1/4)

      Camel-FTP component does not set CamelFtpReplyCode in some case. The attached reproducer can simulate the issue with the reply code 530. It seems like the issue occurs when the reply code is 500.

        1. reproducer.zip
          9 kB

              atarocch@redhat.com Andrea Tarocchi
              rhn-support-hfuruich Hisao Furuichi
              Vratislav Hais Vratislav Hais (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: