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

The error is not appeared in the integration log with Webhook step

XMLWordPrintable

    • % %
    • fuse-7.7-build6
    • +
    • Automated
    • Hide
      • Create Webhook -> Invoke SQL integration
      • As a query, use invalid query like INSERT INTO contact (create_date) VALUES ('Red Hat')
      • Publish integration and invoke Webhook
      • Look to the integration activity tab / the log in the integration pod
      • Change Webhook step to timer step
      • Republish integration
      • Look to the integration activity tab / the log in the integration pod
      Show
      Create Webhook -> Invoke SQL integration As a query, use invalid query like INSERT INTO contact (create_date) VALUES ('Red Hat') Publish integration and invoke Webhook Look to the integration activity tab / the log in the integration pod Change Webhook step to timer step Republish integration Look to the integration activity tab / the log in the integration pod

      When I use Incoming Webhook step in the integration, the error is doesn't show in the integration log.

      When I check `Include error message in the return body` the error is shown at least in the webhook response, but still, the activity log looks as the integration passed successfully.

      When I change the Webhook step to Timer step, the error is shown.

      Syndesis version: 1.10.0-20200518
      Master branch contains little bit different issue, there is thrown a NPE. https://issues.redhat.com/browse/ENTESB-13812

        1. errorIsShown.png
          errorIsShown.png
          381 kB
        2. missingError.png
          missingError.png
          209 kB
        3. Screenshot from 2020-05-28 12-42-20.png
          Screenshot from 2020-05-28 12-42-20.png
          348 kB

            kstam@redhat.com Kurt Stam (Inactive)
            mkralik@redhat.com Matej Kralik
            Matej Kralik Matej Kralik
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: