Return-Path: X-Original-To: apmail-qpid-users-archive@www.apache.org Delivered-To: apmail-qpid-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CCEBEDBA7 for ; Tue, 21 Aug 2012 14:42:44 +0000 (UTC) Received: (qmail 22200 invoked by uid 500); 21 Aug 2012 14:42:44 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 22176 invoked by uid 500); 21 Aug 2012 14:42:44 -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 22166 invoked by uid 99); 21 Aug 2012 14:42:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2012 14:42:44 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.161.170] (HELO mail-gg0-f170.google.com) (209.85.161.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2012 14:42:37 +0000 Received: by ggmo6 with SMTP id o6so5325805ggm.15 for ; Tue, 21 Aug 2012 07:42:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding :x-gm-message-state; bh=hHyYOMdpikkAS3lRW1xvdMw8XG5sYAZf1v5DvHs0woY=; b=kg9GpL+KBwmzg3FrZwC6Xx18Tc8mos/sTffu0Bw2SMnXhoTwWCrLZeN+T/00o356Su mVkISUxkhuBebyMVp1GA4zstuYT9UUK+UIQCGeRljkRB/W7NLvg3Yio+4jVE3ckgUL3J yqjnc8LKw6zujpKipU5g3v1RyxI3AaQjE9p15IzW4Mv7+IFT1vyDr7NB7JzeYwWcFM7c OE6vHFOCMe3jDebkKfrfVTHbOKhl4wm2K19VjEsXu89YJtDinQNDPo9P7dYMa2f6Y9YZ OTXBWqRVmuRKzyLfm9qVzP8w/JyATfdrsEBF4DVqGgbVFckawltfPBjn7O5339QwMJWN oSxw== MIME-Version: 1.0 Received: by 10.50.213.73 with SMTP id nq9mr13796898igc.10.1345560135453; Tue, 21 Aug 2012 07:42:15 -0700 (PDT) Received: by 10.43.71.69 with HTTP; Tue, 21 Aug 2012 07:42:15 -0700 (PDT) X-Originating-IP: [193.29.76.37] In-Reply-To: References: <50339885.4020301@redhat.com> Date: Tue, 21 Aug 2012 16:42:15 +0200 Message-ID: Subject: Re: java no-auth From: Jakub Scholz To: users@qpid.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlbcVf5j2cujN/Ip94JK6gFHz4/QQ1UK/adPJmcBCK6j8UwGesukqpHxqAJOOBNclx2ZzoJ X-Virus-Checked: Checked by ClamAV on apache.org Hi Laurent, Do you need to use the qpid-config tool? Can't you configure the exchanges/queues either in the virtualhosts.xml file or using the JMX Management Console? Regards Jakub On Tue, Aug 21, 2012 at 4:19 PM, wrote: > Hi Gordon, > > Yes, I think I went slightly further -> > > python qpid-config -b guest/guest@192.168.1.3:5672 add exchange topic Msg= Server --durable --sequence > > gives me this > > Failed: NotFound: no such queue: qmf.default.topic > > I just want to replicate in the java world the setup I have with qpidd. W= hich boils down to being able to run the broker with auth=3Dno and with a t= opic that would be created by the pyton script above. If there was a way to= populate virtualhosts.xml that would be wonderful but I am not sure that's= doable at the moment... > > Kind Regards > > -----Original Message----- > From: Gordon Sim [mailto:gsim@redhat.com] > Sent: 21 August 2012 16:18 > To: users@qpid.apache.org > Subject: Re: java no-auth > > On 08/21/2012 01:03 PM, Laurent.Decorps@sungard.com wrote: >> Hello there, >> >> I would like to run the qpid-config python script against the java qpid-= server. >> >> When I do something like >> >> python qpid-config add exchange topic MsgServer --durable --sequence >> >> I get >> >> Failed: AuthenticationFailure: sasl negotiation failed: no mechanism >> agreed > > You can get around that by specifying a username and password as part of = the broker url e.g. -b guest/guest@myhost:5672. That will enable PLAIN on t= he client which should succeed. > >> If I was to run the Cpp version, qpidd with no-auth, that would work nic= ely. >> >> Now my question is: what do I need to configure to run my java server wi= th the "no-auth" cpp equivalent ? > > As above, one option is to use the guest/guest account which exists by de= fault. Alternatively you can enable ANONYMOUS support for qpid-server, but = I'll have to defer to others for details on how to accomplish that. > > One word of warning however, is that the python based command line tools = such as qpid-config were developed against qpidd and so don't work perfectl= y against qpid-server for all cases. Creating and deleting is ok, querying = tends to give confusing results. Even worse however, for the upcoming 0.18 = release they don't work at all. > > If you can describe your use case there may be some suggestion on alterna= te ways to accomplish it that may cause less frustration. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org > For additional commands, e-mail: users-help@qpid.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org > For additional commands, e-mail: users-help@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org