From users-return-19902-archive-asf-public=cust-asf.ponee.io@qpid.apache.org Fri Feb 1 09:27:17 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 6B083180627 for ; Fri, 1 Feb 2019 10:27:17 +0100 (CET) Received: (qmail 27496 invoked by uid 500); 1 Feb 2019 09:27:16 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 27474 invoked by uid 99); 1 Feb 2019 09:27:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2019 09:27:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 36971C036D for ; Fri, 1 Feb 2019 09:27:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.499 X-Spam-Level: ** X-Spam-Status: No, score=2.499 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id RlXPNqitrxym for ; Fri, 1 Feb 2019 09:27:13 +0000 (UTC) Received: from smtp-out-mpa.ailair.net (smtp-out-mpa.ailair.net [176.31.62.6]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 1AF7060CDB for ; Fri, 1 Feb 2019 09:27:13 +0000 (UTC) Received: from Spooler by smtp-out-mpa.ailair.net (Mercury/32 v4.80.145) ID MO037F73; 1 Feb 2019 10:27:12 +0100 Received: from spooler by green.ailair.fr (Mercury/32 v4.80.149); 1 Feb 2019 10:27:06 +0100 Received: from srv-vitmx07.vitechnology.net (79.141.4.209) by smtp-out-mpa.ailair.net (Mercury/32 v4.80.145) with ESMTP ID MG037F70; 1 Feb 2019 10:26:59 +0100 Received: from SRV-VITMX07.vitechnology.net (172.16.4.117) by srv-vitmx07.vitechnology.net (172.16.4.117) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Fri, 1 Feb 2019 10:26:59 +0100 Received: from SRV-VITMX07.vitechnology.net ([fe80::797b:8e10:1c20:95eb]) by srv-vitmx07.vitechnology.net ([fe80::797b:8e10:1c20:95eb%16]) with mapi id 15.00.1293.002; Fri, 1 Feb 2019 10:26:59 +0100 From: Jean-Charles Bisch To: "users@qpid.apache.org" CC: Cyril Micoud Subject: RE: Connection issues on Qpid Broker-J 7.1.0 Thread-Topic: Connection issues on Qpid Broker-J 7.1.0 Thread-Index: AQHUuggZJdWwMxos9k+IcjAMGo/AN6XKq/Co Date: Fri, 1 Feb 2019 09:26:59 +0000 Message-ID: <1549013071344.7143@vitechnology.com> References: <1549010855998.60787@vitechnology.com> In-Reply-To: <1549010855998.60787@vitechnology.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.16.8.24] Content-Type: multipart/alternative; boundary="_000_15490130713447143vitechnologycom_" MIME-Version: 1.0 --_000_15490130713447143vitechnologycom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RTFM sorry for having sent that message; I found solution in the broker man= ual: "secureOnlyMechanisms" : [], sorry for the interruption Best regards Jean-Charles Bisch ________________________________ De : Jean-Charles Bisch Envoy=E9 : vendredi 1 f=E9vrier 2019 09:50 =C0 : users@qpid.apache.org Cc : Cyril Micoud Objet : Connection issues on Qpid Broker-J 7.1.0 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 - pi= d[17979] 17:48:21.281122 AMQP LOG ERROR AMQPBrokerHandler::on_transport_error - = pid[17979]: [amqp:unauthorized-access] - [Authentication failed [mech=3Dnon= e]] 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) : P= rotocol 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 --_000_15490130713447143vitechnologycom_--