qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robbie Gemmell <robbie.gemm...@gmail.com>
Subject Re: Connection issues on Qpid Broker-J 7.1.0
Date Fri, 01 Feb 2019 09:27:21 GMT
You are restricting your client to using PLAIN but Broker-J doesnt
offer PLAIN by default unless SSL/TLS is in use, though you can
configure it to do so. If as it appears you arent using SSL/TLS then
I'd guess your old broker was configured that way and the new one is
not.

If thats the case you could either do that again (see note at
http://qpid.apache.org/releases/qpid-broker-j-7.1.0/book/Java-Broker-Security.html#Java-Broker-Security-Authentication-Providers),
or you could stop instructing the client to only use PLAIN and instead
use a different SASL mechanism (as I expect the Java client is).

Robbie

On Fri, 1 Feb 2019 at 09:03, Jean-Charles Bisch <jbisch@vitechnology.com> wrote:
>
> High all,
>
>
> I am new on qpid project. I had to take responsibility of a qpid proton C++ client library.
I had a lot of issues linked to non respect of good proton object use policy. Hopefully, this
is now over !
>
>
> Our brocker was migrated from Qpid Broker-J 7.0.6 to 7.1.0.
>
> After that, my client was no more able to connect.
>
>
> on the client log side I have:
>
>
> 17:48:21.275355 AMQP LOG INFO         AMQPBrokerHandler::on_container_start - pid[17979]
>
> 17:48:21.281071 AMQP LOG DEBUG    AMQPBrokerHandler::on_transport_open - pid[17979]
>
> 17:48:21.281122 AMQP LOG ERROR     AMQPBrokerHandler::on_transport_error - pid[17979]:
[amqp:unauthorized-access] - [Authentication failed [mech=none]]
>
>
> in the broker logs I have:
>
> 2019-01-31 16:20:02,861 INFO  [Broker-Config] (q.m.c.open) - [con:558(/172.16.8.24:45732)]
CON-1001 : Open : Destination : AMQP(172.16.5.110:5672) : Protocol Version : 1.0
> 2019-01-31 16:20:02,861 INFO  [Broker-Config] (q.m.c.dropped_connection) - [con:558(/172.16.8.24:45732)]
CON-1004 : Connection dropped
>
>
> the code was functional in 7.0.6 and the mechanism used is PLAIN.
>
> The client is wrotten in C++ 98 and on a quite old linux OS: OpenSuse 12.1
>
> The qpid proton library is the latest one: 0.26
>
> The broker is on Windows...
>
> The server written in java is still able to connect on the broker
>
>
> The connection options are following:
>
>         proton::connection_options options;
>         options.user(p_user);
>         options.password(p_password);
>
>         options.sasl_enabled(true);
>         options.sasl_allow_insecure_mechs(true);
>         options.sasl_allowed_mechs("PLAIN");
>
>         //Virtual host
>         if(!p_virtualHost.empty())
>         {
>             options.virtual_host(p_virtualHost);
>         }
>
>         proton::reconnect_options recoOpts;
>         recoOpts.delay(proton::duration(100));
>         recoOpts.max_attempts(40);
>         recoOpts.delay_multiplier(1.0);
>         options.reconnect(recoOpts);
>
>
> Do you think my issue is linked to misconfiguration ?
>
> To a new unknown issue in the broker ?
>
> Is it a way to have more traces on authentification process ?
>
>
>
> Thanks in advance for your help
>
> Best regards
>
> Jean-Charles Bisch
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message