Mule
  1. Mule
  2. MULE-6010

Echo and logger components: performance and behavior issues

    Details

    • User impact:
      Medium
    • Configuration:
      Hide

      Any config using echo component will do.

      Show
      Any config using echo component will do.
    • Migration Impact:
      Echo will no longer log, but this is not vital for production systems.
    • Similar Issues:
      MULE-6147The behavior of processors that have no return value are inconsistent
      MULE-6305Make Message Logger lazy
      MULE-3473CXF requires serviceClass attribute in echo example which uses different interface than what component implements
      MULE-8134JUL loggers are not bridged to log4j2
      MULE-6117Create a new Echo example
      MULE-4337Performance Issue in EventCorrelator
      MULE-141Typos on Echo Example documentation
      MULE-7448Logger - Avoid evaluating expressions when not logging the result
      MULE-6754Introducing a logger between a component and a transformer causes an exception and (possibly changes the payload in some way)
      MULE-5770Secure echo does not work in Notifications example

      Description

      This improves on two issues:

      • Echo component is NOT a logger component, but Logger component IS an Echo component: Hierarchy is reverted.
      • Logger component should only assemble the message to be logged if the proper log level is enabled. Otherwise it assembles a message that will not be used.

      Since lots of users mock external services using echo, especially for performance measurements, it's very important that echo is as lightweight as possible.

      Also, production systems using logger would suffer if for each message that they don't want to be logged, all the message is assembled and then discarded.

        Activity

        Hide
        Victor Bonillo added a comment -

        Fixed in rev 23593.

        Show
        Victor Bonillo added a comment - Fixed in rev 23593.
        Hide
        Alejandro Sequeira added a comment -

        Victor Bonillo, please close it if it is already fixed for 3.3 and 3.2.

        Show
        Alejandro Sequeira added a comment - Victor Bonillo , please close it if it is already fixed for 3.3 and 3.2.
        Hide
        Victor Bonillo added a comment -

        Not fixed yet. Changes were rolled back and postponed, since they caused problems with streaming.
        Alejandro Sequeira, please add to to-do list for next versions.

        Show
        Victor Bonillo added a comment - Not fixed yet. Changes were rolled back and postponed, since they caused problems with streaming. Alejandro Sequeira , please add to to-do list for next versions.
        Hide
        Steven Camina added a comment - - edited

        Is there an update for this issue? It's been over a year...

        Show
        Steven Camina added a comment - - edited Is there an update for this issue? It's been over a year...
        Hide
        Ramiro Rinaudo added a comment -

        Please reopen if there is still a problem.

        Show
        Ramiro Rinaudo added a comment - Please reopen if there is still a problem.

          People

          • Assignee:
            Victor Bonillo
            Reporter:
            Victor Bonillo
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development