Qpid
  1. Qpid
  2. QPID-2599

Allow Qpid users to configure the Java client logging using an sl4j binding of their choice, instead of Qpid shipping a defualt binding.

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.5, 0.6
    • Fix Version/s: 0.7
    • Component/s: Java Client
    • Labels:
      None

      Description

      All though we have a logging facade (slf4j) in the java client, we complicate the situation by shipping slf4j-log4j binding along with our release artifacts.
      If not configured properly log4j will default to using DEBUG which degrades the performance.
      The situation complicated as we have a whole bunch of log4j.xmls and property files lying all over the place.

      We have discussed and arrived at some consensus on the following thread.
      http://apache-qpid-developers.2158895.n2.nabble.com/Java-Client-Logging-yet-again-td4696020.html#a4696020

      The action plan for solving this includes.

      1. Remove all log4j.xml and log4j.properties files from the code based
      (except for the ones in broker/etc )

      2. Remove slf4j-log4j.jar from our release artefacts.
      The reason this is present in the java/lib folder is due to our test framework relying on log4j for capturing client logs for debug.

      3. Document clearly the logging mechanism in the
      "Programming-In-Apache-Qpid' guide."
      This should include how one could change to a different slf4j binding

      4. Upstream packages could use a binding of their choice.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Rajith Attapattu
            Reporter:
            Rajith Attapattu
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development