Hi all, I have a curious behavior, with qpid messaging + qpid proton (I used the latest version from https://launchpad.net/~qpid/+archive/ubuntu/testing) (built for debian by my obs) I use activemq (latest version 5.14) amqp 1.0. On my linux distribution (debian jessie) all works perfectly, connection, and all features (topics, queue, etc.)
On my arm (v7) and the same linux distrib, I can not establish a connection with the broker. I set QPID_LOG_ENABLE="debug" and here is the log: [Messaging] debug Driver started [Messaging] debug tcp:X.X.X.X:5672 Connecting ... [Client] debug Set TCP_NODELAY [Messaging] debug tcp:X.X.X.X:5672 Connected [Messaging] debug wakeupDriver() [Messaging] debug tcp:X.X.X.X:5672 Waiting to be authenticated... [Protocol] debug tcp:X.X.X.X:5672 writing protocol header: 1-0 [Protocol] debug tcp:X.X.X.X:5672 read protocol header: 1-0 [Protocol] debug tcp:X.X.X.X:5672 Received SASL-MECHANISMS(PLAIN ANONYMOUS ) [Security] debug CyrusSasl::start(PLAIN ANONYMOUS ) [Security] debug min_ssf: 0, max_ssf: 256 [System] debug Exception constructed: Can't authenticate using PLAIN ANONYMOUS [Messaging] debug [166.99.224.106:57613-X.X.X.X:5672] TcpTransport closing... [Messaging] debug [166.99.224.106:57613-X.X.X.X:5672] Socket closed connection exception 'Can't authenticate using PLAIN ANONYMOUS ' [Messaging] debug Driver stopped and in wireshark I have not the sasl.init, like if the sasl library throw an exception, and after nothing!!! it's annoying, because my target is arm!!!! more over i use the boost library (1.55) too, I don't know if there is a issue with this dependency ??? Thanks for your help Regards Xavier -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-client-1-35-arm-v7-tp7651580.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
