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

Hawtio:Camel: fatal error logs in terminal after sending empty message

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • fuse-7.1
    • fuse-7.0.1
    • Hawtio, Karaf
    • None
    • % %
    • Hide

      1. Login to Hawtio
      2. In terminal, start the camel-cbr beginner quickstart
      3. Go to Camel tab in Hawtio
      4. Choose some endpoint and open it (I chose file://work/cbr/input)
      5. Go to Send tab
      6. Leave the body empty and click on Send message
      7. Check the terminal

      Show
      1. Login to Hawtio 2. In terminal, start the camel-cbr beginner quickstart 3. Go to Camel tab in Hawtio 4. Choose some endpoint and open it (I chose file://work/cbr/input ) 5. Go to Send tab 6. Leave the body empty and click on Send message 7. Check the terminal
    • Fuse 7.1 Sprint 32

      Current behavior:
      In the terminal, there are constantly running messages with this text:
      [Fatal Error] :-1:-1: Premature end of file.
      It doesn't seem like some appropriate behaviour from user point of view. Using of the terminal after this becomes very problematic. The error messages are also in logs with more detailed description.

      Expected behaviour:
      The error messages about wrong body or type of message are visible only in the logs.

        1. camel-errors.webm
          3.09 MB

            [ENTESB-9195] Hawtio:Camel: fatal error logs in terminal after sending empty message

            Lucia Drozdova (Inactive) added a comment -

            Hello,
            issue tested correctly on fuse-karaf-7.1.0.fuse-710017, RHEL 7, Chrome 65.0.3325.181.
            Thank you.

            Lucia Drozdova (Inactive) added a comment - Hello, issue tested correctly on fuse-karaf-7.1.0.fuse-710017, RHEL 7, Chrome 65.0.3325.181. Thank you.

            Grzegorz Grzybek added a comment - - edited

            Fixed here in jboss-fuse/fuse-karaf/7.1.x.redhat-7-1-x branch.

            Grzegorz Grzybek added a comment - - edited Fixed here in jboss-fuse/fuse-karaf/7.1.x.redhat-7-1-x branch.

            Grzegorz Grzybek added a comment -

            PR: https://github.com/jboss-fuse/fuse-karaf/pull/170

            Grzegorz Grzybek added a comment - PR: https://github.com/jboss-fuse/fuse-karaf/pull/170

            Lucia Drozdova (Inactive) added a comment - - edited

            Hello,
            issue tested on fuse-karaf-7.1.0.fuse-710013, RHEL 7, Chrome 65.0.3325.181.
            It's fixed for camel-cbr, thank you. But I also tried it with another quickstarts, and for camel-eips it's still NOK. I tested it with file://work/eip/input endpoint.
            Can you please fix it for all quickstarts?

            Lucia Drozdova (Inactive) added a comment - - edited Hello, issue tested on fuse-karaf-7.1.0.fuse-710013, RHEL 7, Chrome 65.0.3325.181. It's fixed for camel-cbr, thank you. But I also tried it with another quickstarts , and for camel-eips it's still NOK . I tested it with file://work/eip/input endpoint. Can you please fix it for all quickstarts?

            Grzegorz Grzybek added a comment -

            Fixed here in jboss-fuse/fuse-karaf/7.1.x.redhat-7-1-x branch.

            Grzegorz Grzybek added a comment - Fixed here in jboss-fuse/fuse-karaf/7.1.x.redhat-7-1-x branch.

            Grzegorz Grzybek added a comment -

            PR: https://github.com/jboss-fuse/fuse-karaf/pull/164

            Grzegorz Grzybek added a comment - PR: https://github.com/jboss-fuse/fuse-karaf/pull/164

            Alexandre Kieling added a comment -

            ggrzybek Can you have a look at this issue?

            Alexandre Kieling added a comment - ggrzybek Can you have a look at this issue?

            James Netherton added a comment -

            Yes because it's specifically about what happens to the Karaf CLI when errors start occurring.

            James Netherton added a comment - Yes because it's specifically about what happens to the Karaf CLI when errors start occurring.

            Alexandre Kieling added a comment -

            Does this issue happen only in Karaf?

            Alexandre Kieling added a comment - Does this issue happen only in Karaf?

            James Netherton added a comment -

            I think it would be better to fix this issue in Karaf to prevent the log messages from messing up the console.

            Hawtio does not know what processing the camel application is going to do on the payload. So it's possible to send a message body that the Camel route(s) may not be able to handle gracefully. The user needs to ensure that what they send to the endpoint is valid for their application.

            Empty message bodies should be allowed as it's not mandatory for a Camel route to expect a body to be present on the exchange. E.g some components can work exclusively with headers and not require a message body.

            James Netherton added a comment - I think it would be better to fix this issue in Karaf to prevent the log messages from messing up the console. Hawtio does not know what processing the camel application is going to do on the payload. So it's possible to send a message body that the Camel route(s) may not be able to handle gracefully. The user needs to ensure that what they send to the endpoint is valid for their application. Empty message bodies should be allowed as it's not mandatory for a Camel route to expect a body to be present on the exchange. E.g some components can work exclusively with headers and not require a message body.

              ggrzybek Grzegorz Grzybek
              ldrozdo Lucia Drozdova (Inactive)
              Lucia Drozdova Lucia Drozdova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: