Hi Andreas, I added that tool to check if the proton-j codecs was working properly.
On Tue, Jul 3, 2012 at 7:59 AM, Andreas Mueller <[email protected]> wrote: > Hi, > > there is actually no need to write your own tools because there are plenty > of ways to get what you want. > > 1) The best tool to see what's going with AMQP 1.0 on TCP level is > iAmqpDecode from INETCO. Download here (near bottom of page): > > http://www.inetco.com/resource-library/technology-amqp/ > > 2) If you use > > -Dswiftmq.amqp.frame.debug=true > > at the SwiftMQ AMQP 1.0 client, you'll get frame debug output. > > 3) Same can be done on the broker side: > > > http://www.swiftmq.com/products/router/swiftlets/sys_amqp/monitoring/index.html > (see Tracing and Debugging) > > Cheers, > Andreas > -- > Andreas Mueller > IIT Software GmbH, Bremen/Germany > http://www.swiftmq.com > > > > > > IIT Software GmbH > Fahrenheitstr. 1, D28359 Bremen, Germany > Tel: +49 421 2208-166, Fax: +49 421 2208-167 > Amtsgericht Bremen, HRB 18624, Geschaeftsfuehrer: Andreas Mueller > Steuernummer: 71/572/04100, VAT: DE199945912 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- ** *Hiram Chirino* *Software Fellow | FuseSource Corp.* *[email protected] | fusesource.com* *skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchirino> * *blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>* * * * *
