Hi Kyle, That suggest that the client is using AMQP 0-10 and so has sent the broker the 0-10 protocol header, and the broker responded with the AMQP 0-9-1 header (which is presented as 9-1..) indicating that it doesnt support 0-10.
It should only do that if the particular AMQP port becing connected to was been configured to support specific protocol versions and 0-10 isnt one of them, or the protocol was disabled broker-wide, as by default all protocol versions are enabled on the ports. Robbie On 30 January 2014 19:50, Kyle Crumpton (kcrumpto) <[email protected]>wrote: > > > Hi all. > > I'm using the Java Broker version 0.22 with a patch by Mr. Godfrey to > allow binding to separate interfaces for AMQP and HTTP. > Right now qpid is listening on the IP "127.1.245.130" > > I deployed qpid on my PaaS. If I do "netstat -na | grep 5672" > > tcp6 0 0 127.1.245.130:5672 :::* LISTEN > > I was having issues communicating with this. So I pulled this code: > http://qpid.apache.org/releases/qpid-0.22/messaging-api/python/examples/hello.html > and changed the host to 127.1.245.130:5672. > > The message I get when I run the code is: > > client: 0-10, server: 9-1 > > which is the exception message. > > Any clues what's going on here? Thanks a bunch > > Kyle Crumpton > > > >
