The C examples dont set credentials and will use a bare AMQP connection without them, meaning without establishing the SASL layer first, with your note of AMQP,0,1,0,0 (the 'bare' AMQP 1.0 header) confirming it. http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-security-v1.0-os.html#section-sasl. If the server doesnt allow/support that type of raw unauthenticated connection, as I believe activemq 5 doesnt by default, then it would be expected to refuse the connection and indicate it needs the SASL layer by sending its header back (AMQP,3,1,0,0). I expect that what happened here.
The simplest change is likely to provide any credentials required, e.g see https://qpid.apache.org/releases/qpid-proton-0.39.0/proton/c/api/group__connection.html#gafb84dd2ef7551ad864be08cb31010d19. You could alternatively explicitly enable the sasl layer to e.g do ANONYMOUS sasl, or configure the broker to actually allow the raw connections. On Tue, 7 Nov 2023 at 09:39, Alec Finexus <chuanfine...@gmail.com> wrote: > > Hi Qpid Apacha team, > > I am using pqid proton C 0.40.0-Dev with Apache ActiveMQ 5.18.2. > When I tried to execute the send program, I encountered error "Connection > from client using unsupported AMQP attempted" which I am confused because > the paid proton C is using AMQP,0,1,0,0 which should be matching AMQP v1.0. > > Same goes to the receive program. Kindly advise on this case. Thanks > > Best Regards > Alec --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
