Open grs opened 6 years ago
Thanks @grs for these details!! I will try to repro :)
The only thing I can answer off the top of my head is the 100% CPU use - I generally assume that establishing the connection and authentication will a be quick process and therefore I made no effort to slow down iterating the connection as much as possible during this process.
Clearly this assumption is invalid in circumstances where:
So I will revisit the design there.
Again, thanks!
I've tripped across this issue as well when trying to use uAMQP against an ActiveMQ Artemis server.
If it helps I get an error in the artemis.log file on the broker:
AMQ224096: Error setting up connection from /localhost:53814 to /localhost:5672; protocol CORE not found in map: [AMQP]
For my test I tried using both plain and anonymous authentication. Both cause the same error on the broker and the client just hangs.
Thanks for the report @egandone - I would really like to invest the time in getting this project working with these other AMQP servers - though unfortunately I wont be able to in the immediate future :(
I will hopefully be able to revisit this in the coming months as we are on-boarding more people to help with these projects.
I have been trying to run a simple example client against various different AMQP servers from the Apache Software Foundation (Apache ActivemMQ Artemis, Apache Qpid Dispatch Router and Apache c++ broker aka qpidd).
In all cases I am unable to connect. My test client is as follows:
Viewing the interaction with wireshark, it appears that the client does not emit a valid AMQP protocol header at the start of the stream. I see 16 03 01 00 ab 01 00 00 seemingly every time as the first 8 bytes. The client then seems to spin in a loop, with cpu going to 100%.
If it is useful for testing, you can use:
To start an instance of qpid dispatch router listening on 5672 (no TLS, no auth required).