Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-6961

Make Camel core bundle configurable to generate less or smaller log messages itself

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: 2.12.1
    • Fix Version/s: 2.12.2, 2.13.0
    • Labels:
      None
    • Environment:

      Karaf osgi container, blueprint configuration

    • Estimated Complexity:
      Unknown

      Description

      Currently the Camel core generates easily lots of warning/error messages within the local log file. This makes it almost impossible to search for errors caused by other bundles, because the Camel bundle fills up about 99% of the log file content. Because the runtime will only store up to 11 log files log events are hard to find and also lost rather quickly (because older log files get deleted).
      Looking through Camel code we can find something like this:

      if (endpoint.getConsumer() == null) {
                  LOG.warn("No consumers available on endpoint: " + endpoint + " to process: " + exchange);
                  throw new DirectConsumerNotAvailableException("No consumers available on endpoint: " + endpoint, exchange);
              } else { 
      

      The entire exchange put to the log before exception was thrown. It makes a huge log entries, which can not be turn off, unless we lost all the logs from Camel bundle.
      It will be very useful to have camel bundle logs configurable, to get more or less details by demand.

        Attachments

          Activity

            People

            • Assignee:
              davsclaus Claus Ibsen
              Reporter:
              rminko Roman Minko
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: