Hi Erik, I think the most likely answer is that none of us really use that logger and so haven't noticed the disparity :)
I just pushed a change to use the BYTES logger for the incoming data as well for consistency with the outgoing data handling in that class, as the trace message that was being logged at that point was mainly a repeating of some previous transport logging anyway. Robbie On 5 June 2015 at 09:21, Erik Aschenbrenner <easch...@icubic.de> wrote: > Dear Qpid users, > > the old Qpid client API used the loggers "FRM" and "RAW". These were > replaced by the loggers "org.apache.qpid.jms.provider.amqp.FRAMES" and > "org.apache.qpid.jms.provider.amqp.BYTES". The byte logger only logs sent > data. Why doesn't it log the received data also? This would be interesting > for debugging message encoding errors or not? > > Regards, > Erik > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Changing-from-old-Qpid-JMS-client-to-Qpid-JMS-0-2-0-tp7625652p7625883.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
