Uploaded image for project: 'Qpid Dispatch'
  1. Qpid Dispatch
  2. DISPATCH-482

trace level log messages are printing out as null

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.7.0
    • 0.7.0
    • Container
    • None
    • CentOS 6 i686

    Description

      Make sure you are testing this on a CentOS 6 i686 environment

      Add the following to your dispatch router config file (qdrouterd.conf)

      log {
          module: DEFAULT
          enable: trace,debug+
          timestamp: yes
      }
      

      Start the dispatch router and attach a receiver using python proton's simple_recv.py like this

      python simple_recv.py -m1
      

      You will see the following TRACE output on the console

      Fri Aug 26 12:44:48 2016 SERVER (info) Operational, 4 Threads Running
      Fri Aug 26 12:44:52 2016 POLICY (trace) ALLOW Connection '127.0.0.1:40891' based on global connection count. nConnections= 1
      Fri Aug 26 12:44:52 2016 SERVER (debug) Accepting incoming connection from 127.0.0.1:40891 to 0.0.0.0:amqp
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]: (null)
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]: (null)
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]: (null)
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]: (null)
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]: (null)
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]: (null)
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]: (null)
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]: (null)
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]: (null)
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]:  (null)
      
      

      Notice the (null) above. The TRACE message should instead look like the following-

      Fri Aug 26 12:44:48 2016 SERVER (info) Operational, 4 Threads Running
      Fri Aug 26 12:44:52 2016 POLICY (trace) ALLOW Connection '127.0.0.1:40891' based on global connection count. nConnections= 1
      Fri Aug 26 12:44:52 2016 SERVER (debug) Accepting incoming connection from 127.0.0.1:40891 to 0.0.0.0:amqp
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]:AMQP SASL layer detected
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]:  <- SASL
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]:  -> SASL
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]:0 -> @sasl-mechanisms(64) [sasl-server-mechanisms=@PN_SYMBOL[:"DIGEST-MD5", :ANONYMOUS, :PLAIN]]
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]:RAW: "\x00\x00\x00B\x02\x01\x00\x00\x00S@\xd0\x00\x00\x002\x00\x00\x00\x01\xf0\x00\x00\x00)\x00\x00\x00\x03\xb3\x00\x00\x00\x0aDIGEST-MD5\x00\x00\x00\x09ANONYMOUS\x00\x00\x00\x05PLAIN"
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]:0 <- @sasl-init(65) [mechanism=:ANONYMOUS, initial-response=b"anonymous@livecd.centos"]
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]:Authenticated user: anonymous with mechanism ANONYMOUS
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]:0 -> @sasl-outcome(68) [code=0]
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]:RAW: "\x00\x00\x00\x16\x02\x01\x00\x00\x00SD\xd0\x00\x00\x00\x06\x00\x00\x00\x01P\x00"
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]:AMQP 1.0 layer detected
      Fri Aug 26 12:44:52 2016 SERVER (trace) [1]:  <- AMQP
      
      

      Attachments

        Activity

          People

            gmurthy Ganesh Murthy
            gmurthy Ganesh Murthy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: