1. Qpid
  2. QPID-4655

[Java Broker] add BrokerOptions support to request the Broker not perform log4j logging configuration when it is being run embedded


    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.21
    • Component/s: Java Broker
    • Labels:


      The broker configures Log4J at startup due to its heritage of running in a standalone VM. We have made the broker easier to run embedded in recent times, but it still always configures Log4J at startup. It was requested that we enable preventing it from doing this so the embedding application can configure things itself.

      Support will be added to the BrokerOptions object to allow requesting the Broker instance not perform log4j logging configuration when it is being run embedded. This will also prevent the brokers LoggingManagement MBean from being initialised, as it is dependant on the logging configuration perfomed by the broker and it also has direct support for managing the Log4j configuration file which may not exist in this case.


        Robbie Gemmell created issue -
        Robbie Gemmell made changes -
        Field Original Value New Value
        Status Open [ 1 ] In Progress [ 3 ]
        Robbie Gemmell made changes -
        Status In Progress [ 3 ] Ready To Review [ 10006 ]
        Robbie Gemmell made changes -
        Assignee Robbie Gemmell [ gemmellr ] Alex Rudyy [ alex.rufous ]
        Alex Rudyy made changes -
        Status Ready To Review [ 10006 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Rob Godfrey made changes -
        Status Resolved [ 5 ] Closed [ 6 ]


          • Assignee:
            Alex Rudyy
            Robbie Gemmell
          • Votes:
            0 Vote for this issue
            2 Start watching this issue


            • Created: