Hey Rob, You're right. I didn't see that Python uses 0-10. I am using just 0.9.1.
I seem to be having trouble communicating with it across that IP in general, though. On 1/30/14 2:03 PM, "Rob Godfrey" <[email protected]> wrote: >Hi Kyle, > >the error message you're getting there would seem to indicate that the >broker is configured to accept connections using the AMQP 0-9-1 protocol, >but not those using AMQP 0-10 (the python client uses AMQP 0-10). Out of >the box the Java Broker allows connections for all published versions of >the AMQP protocol (0-8, 0-9, 0-9-1, 0-10 and 1-0)... have you configured >your broker to not accept some versions of the protocol? > >-- Rob > > >On 30 January 2014 20: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/h >>ello.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 >> >> >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
