You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Kyle Crumpton (kcrumpto)" <kc...@cisco.com> on 2014/01/30 20:50:40 UTC
Java broker communication error
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
Re: Java broker communication error
Posted by Robbie Gemmell <ro...@gmail.com>.
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) <kc...@cisco.com>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
>
>
>
>
Re: Java broker communication error
Posted by "Kyle Crumpton (kcrumpto)" <kc...@cisco.com>.
Mind hopping on IRC for a sec?
On 1/30/14 2:22 PM, "Rob Godfrey" <ro...@gmail.com> wrote:
>Where are you getting this error, broker or client (and if the latter -
>which client are you using)?
>
>-- Rob
>
>
>On 30 January 2014 21:19, Kyle Crumpton (kcrumpto)
><kc...@cisco.com>wrote:
>
>> Hi Rob. It says that is "closing unexpected channel"
>> AMQChannel(amqp://guest@127.1.245.130).
>>
>> On 1/30/14 2:13 PM, "Rob Godfrey" <ro...@gmail.com> wrote:
>>
>> >OK - the fact that the Python got that error at least shows it made a
>> >connection (albeit not a very long lasting one :-) ).
>> >
>> >What is the nature of the issues you are having when trying to
>>communicate
>> >to that IP?
>> >
>> >-- Rob
>> >
>> >
>> >On 30 January 2014 21:05, Kyle Crumpton (kcrumpto)
>> ><kc...@cisco.com>wrote:
>> >
>> >> 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" <ro...@gmail.com> 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)
>> >> ><kc...@cisco.com>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: dev-unsubscribe@qpid.apache.org
>> >> For additional commands, e-mail: dev-help@qpid.apache.org
>> >>
>> >>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: dev-help@qpid.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Java broker communication error
Posted by Rob Godfrey <ro...@gmail.com>.
Where are you getting this error, broker or client (and if the latter -
which client are you using)?
-- Rob
On 30 January 2014 21:19, Kyle Crumpton (kcrumpto) <kc...@cisco.com>wrote:
> Hi Rob. It says that is "closing unexpected channel"
> AMQChannel(amqp://guest@127.1.245.130).
>
> On 1/30/14 2:13 PM, "Rob Godfrey" <ro...@gmail.com> wrote:
>
> >OK - the fact that the Python got that error at least shows it made a
> >connection (albeit not a very long lasting one :-) ).
> >
> >What is the nature of the issues you are having when trying to communicate
> >to that IP?
> >
> >-- Rob
> >
> >
> >On 30 January 2014 21:05, Kyle Crumpton (kcrumpto)
> ><kc...@cisco.com>wrote:
> >
> >> 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" <ro...@gmail.com> 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)
> >> ><kc...@cisco.com>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: dev-unsubscribe@qpid.apache.org
> >> For additional commands, e-mail: dev-help@qpid.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
> For additional commands, e-mail: dev-help@qpid.apache.org
>
>
Re: Java broker communication error
Posted by "Kyle Crumpton (kcrumpto)" <kc...@cisco.com>.
Hi Rob. It says that is "closing unexpected channel"
AMQChannel(amqp://guest@127.1.245.130).
On 1/30/14 2:13 PM, "Rob Godfrey" <ro...@gmail.com> wrote:
>OK - the fact that the Python got that error at least shows it made a
>connection (albeit not a very long lasting one :-) ).
>
>What is the nature of the issues you are having when trying to communicate
>to that IP?
>
>-- Rob
>
>
>On 30 January 2014 21:05, Kyle Crumpton (kcrumpto)
><kc...@cisco.com>wrote:
>
>> 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" <ro...@gmail.com> 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)
>> ><kc...@cisco.com>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: dev-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: dev-help@qpid.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Java broker communication error
Posted by Rob Godfrey <ro...@gmail.com>.
OK - the fact that the Python got that error at least shows it made a
connection (albeit not a very long lasting one :-) ).
What is the nature of the issues you are having when trying to communicate
to that IP?
-- Rob
On 30 January 2014 21:05, Kyle Crumpton (kcrumpto) <kc...@cisco.com>wrote:
> 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" <ro...@gmail.com> 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)
> ><kc...@cisco.com>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: dev-unsubscribe@qpid.apache.org
> For additional commands, e-mail: dev-help@qpid.apache.org
>
>
Re: Java broker communication error
Posted by "Kyle Crumpton (kcrumpto)" <kc...@cisco.com>.
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" <ro...@gmail.com> 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)
><kc...@cisco.com>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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Java broker communication error
Posted by Rob Godfrey <ro...@gmail.com>.
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) <kc...@cisco.com>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
>
>
>
>