Many thanks for the response. I checked the manual and HornetQ does support SASL and AMQP is enabled.
The issue (solved with assistance from Justin Bertram on the Jboss forums: https://developer.jboss.org/thread/265676) was a misunderstanding concerning queue configuration. Just in case anyone else tries to do the same thing and finds this, the "correct" config I used included: <queues> <queue name="exampleQueue1"> <address>exampleQueue1</address> <durable>true</durable> </queue> <queue name="exampleQueue2"> <address>exampleQueue2</address> <durable>true</durable> </queue> </queues> And <acceptor name="proton-acceptor"> <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class> <param key="protocols" value="AMQP"/> <param key="host" value="0.0.0.0"/> <param key="port" value="5672"/> </acceptor> With these changes (primarily a queue address change) the example works. Thanks again for the help, and for pointing me to Wireshark which is really useful! -----Original Message----- From: Gordon Sim [mailto:[email protected]] Sent: 23 October 2015 10:09 To: [email protected] Subject: Re: Basic send/receive AMQP message to HornetQ server using Python On 10/23/2015 09:00 AM, Matthew Karlsen wrote: > Hello, > > I am currently attempting to use the code on > https://qpid.apache.org/releases/qpid-proton-0.10/proton/python/tutorial/tutorial.html > to send and receive a message to a HornetQ server. > > (Slightly modified code below...) > > I have set up a HornetQ core queue called exampleQueue1 to connect to and am > running the server. I get, e.g. "08:29:28,247 INFO [org.hornetq.core.server] > HQ221003: trying to deploy queue exampleQueue1" on the server console. > > I have compiled the required c code for the example to run properly. > > When I run the example below I get "ERROR:root:amqp:connection:framing-error: > SASL header mismatch: Insufficient data to determine protocol [''] > (connection aborted)" repeatedly until I kill the program. > > I have googled this error but get very few hits and have not found one that > is sufficiently explanatory. > > I will continue to try to work out how to solve this issue. However, I was > wondering if anyone could assist with this question? It sounds like the client is sending the SASL AMQP protocol header, and the broker is not replying as expected with an AMQP protocol header. You could verify that by running wireshark. Setting PN_TRACE_FRM=1 while running the client will also print some details (but that is the client's view). Is AMQP definitely enabled on the broker? Does the version in use support SASL? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
