From qpid-dev-returnjenniferbrown@example.org Sat Sep 01 22:37:03 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 91490 invoked from network); 1 Sep 2007 22:37:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Sep 2007 22:37:02 -0000 Received: (qmail 4468 invoked by uid 500); 1 Sep 2007 22:36:57 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 4450 invoked by uid 500); 1 Sep 2007 22:36:57 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 4441 invoked by uid 99); 1 Sep 2007 22:36:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Sep 2007 15:36:57 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jenniferbrown@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO rv-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Sep 2007 22:36:53 +0000 Received: by rv-out-0910.google.com with SMTP id k20so682030rvb for <jenniferbrown@example.org>; Sat, 01 Sep 2007 15:36:32 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gNSxtWgPzd4luDmv57IqV4x29w/4WoZXfDRpoU3LttS5ERxBk87QeGS87dIwGH3izizaP2GFhk3MmRV4Pw82mXYzFlrdxWfQh91/MEtpERbniIENtigd1Lbi7ZNPfCnucoGWOIXhAb6KT3m8j1rf01m28e4IGMnjzxF7sRGiolY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qU1VpV2i2OIpAmNjYV7+WyW2uBJ+y/y92c9i05TmDwVzs7If2ypWYJ+x2eEvWs5QjcqbOCVh2nxPkZlGN792fn9dyGlIrtIUxpeKpy7yXb2PZloCHPn1AgjJTDhN8dsBh1t4WxyE1YIJz3gCC8WwIbANqf4bwnO+WjXf1KxWNag= Received: by 83.161.120.155 with SMTP id x7mr1322719rvi.1188686192076; Sat, 01 Sep 2007 15:36:32 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Sat, 1 Sep 2007 15:36:32 -0700 (PDT) Message-ID: <jenniferbrown@example.org> Date: Sat, 1 Sep 2007 23:36:32 +0100 From: "Robert Greig" <jenniferbrown@example.org> To: jenniferbrown@example.org Subject: Re: [ANN] java RC3 available In-Reply-To: <jenniferbrown@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <jenniferbrown@example.org> X-Virus-Checked: Checked by ClamAV on apache.org On 30/08/07, Rajith Attapattu <jenniferbrown@example.org> wrote: > I have tested the java binary with the python tests and it's fine. I have started doing some brief sanity checking and it seems ok - broker starts up fine. I have been looking at improving our documentation on confluence and I had a couple of questions that perhaps people could answer: 1. Why do we have separate access and jmxremote.access files? 2. On starting the broker the following warnings are printed: 2007-09-01 23:07:49,145 WARN [main] access.AMQUserManagementMBean (AMQUserManagementMBean.java:386) - Access rights contains user 'admin' but there is no authentication data for that user 2007-09-01 23:07:49,175 WARN [main] access.AMQUserManagementMBean (AMQUserManagementMBean.java:386) - Access rights contains user 'user' but there is no authentication data for that user Is it deliberate that there are no default values for those users in the passwd file? 3. The etc directory is somewhat confusing for a new user (or even me!). We have the following "passwd" files: md5passwd passwd passwdVhost qpid.passwd Can someone explain the differences between these? I see md5passwd is needed as an example md5 passwd file and passwd is for plain. But what about the others? 4. What is qpid-server.conf.jpp for? RG From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 08:45:30 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 41002 invoked from network); 3 Sep 2007 08:45:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 08:45:29 -0000 Received: (qmail 1877 invoked by uid 500); 3 Sep 2007 08:45:24 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 1771 invoked by uid 500); 3 Sep 2007 08:45:24 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 1762 invoked by uid 99); 3 Sep 2007 08:45:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 01:45:24 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jenniferbrown@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO nf-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 08:45:18 +0000 Received: by nf-out-0910.google.com with SMTP id h3so1207980nfh for <jenniferbrown@example.org>; Mon, 03 Sep 2007 01:44:56 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=WmbTlkVAMBUkEtosg3L3SsXWIrvTbSkmNiQkoldRFG6Gm256Gx/NvUfBAkLF+xzbrhaQNVh4RBAJhgwAkrQ/SxBZClxiAH+9GNYblAVKzFfQWTSKOt2VP9QQwoGR6svxOw2//t/UQ7xVil7TfcSAN5xytDopr6WVVPn08IpWLf4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=f2NO45PAT296HzdiUN+cxRPJ0uXKDhX1xC7NoPVUh2W2yBx77jqdahFGG1pB0ayIkHbQA1949TUdcsg+nkmtyW6rJhfKyxNUuVJmF88TMfM0qrQHbEjJLjt6qjTCwd3SBNWRqwEA08x9dJNw2pIyUxkasujSMnJAnMX2BQn/YLw= Received: by 83.161.120.155 with SMTP id b20mr3020954hug.1188809096101; Mon, 03 Sep 2007 01:44:56 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Mon, 3 Sep 2007 01:44:55 -0700 (PDT) Message-ID: <jenniferbrown@example.org> Date: Mon, 3 Sep 2007 09:44:55 +0100 From: "Martin Ritchie" <jenniferbrown@example.org> Sender: jenniferbrown@example.org To: jenniferbrown@example.org Subject: Re: [ANN] java RC3 available In-Reply-To: <jenniferbrown@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <jenniferbrown@example.org> <jenniferbrown@example.org> X-Google-Sender-Auth: 6f912bee662a9ff3 X-Virus-Checked: Checked by ClamAV on apache.org On 01/09/07, Robert Greig <jenniferbrown@example.org> wrote: > On 30/08/07, Rajith Attapattu <jenniferbrown@example.org> wrote: > > > I have tested the java binary with the python tests and it's fine. > > I have started doing some brief sanity checking and it seems ok - > broker starts up fine. > > I have been looking at improving our documentation on confluence and I > had a couple of questions that perhaps people could answer: > > 1. Why do we have separate access and jmxremote.access files? The jmxremote.access file provides access controls for the JMX management console. Not all users need be listed in this section. This is purely a permission assignment. No authentication credentials are inferred or granted through this file. See 3 below. The access file serves as an example Access Control file for the basic FileAccessManager. Currently only you my only restrict read access to a particular virtualhost as performing the controls on write requires a check on every publish method which will affect performance. When AMQP has ACL/RBAC which I believe is planed for 0_11 then this will be updated accordingly. > 2. On starting the broker the following warnings are printed: > > 2007-09-01 23:07:49,145 WARN [main] access.AMQUserManagementMBean > (AMQUserManagementMBean.java:386) - Access rights contains user > 'admin' but there is no authentication data for that user > 2007-09-01 23:07:49,175 WARN [main] access.AMQUserManagementMBean > (AMQUserManagementMBean.java:386) - Access rights contains user 'user' > but there is no authentication data for that user > > Is it deliberate that there are no default values for those users in > the passwd file? It is simply a case that no-one has updated all the authentication password file to contain these users. The JMX console is not secure unless using encryption on the JMX connection. You need the jmxremote.jar to use a SASL connection which we cannot distribute as its license is not an Apache friendly one. That coupled with the Base64MD5 PasswordFile gives a reasonable level of security. Not great but there you have it. > 3. The etc directory is somewhat confusing for a new user (or even > me!). We have the following "passwd" files: We have a number of different authentication modules each use a different file format. > md5passwd For use with Base64MD5PasswordFile. File contains Base64 encoded hashes of the users password. > passwd For use with PlainPasswordFile. File contains plain text passwords > passwdVhost For use with PlainPasswordVhostFile. File contains plain text passwords and additional Virtualhost authorisation details. > qpid.passwd This is a duplicate of md5passwd. I must have added this by mistake. > Can someone explain the differences between these? I see md5passwd is > needed as an example md5 passwd file and passwd is for plain. But what > about the others? > > 4. What is qpid-server.conf.jpp for? I believe this is some configuration file for JProfiler. It shouldn't be in the broker etc directory, it that is the case. > RG > -- Martin Ritchie From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 09:17:45 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 50335 invoked from network); 3 Sep 2007 09:17:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 09:17:44 -0000 Received: (qmail 34801 invoked by uid 500); 3 Sep 2007 09:17:39 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 34694 invoked by uid 500); 3 Sep 2007 09:17:39 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 34685 invoked by uid 99); 3 Sep 2007 09:17:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 02:17:39 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 09:18:52 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 5B835714163 for <jenniferbrown@example.org>; Mon, 3 Sep 2007 02:17:20 -0700 (PDT) Message-ID: <22594787.1188811040354.JavaMail.jira@brutus> Date: Mon, 3 Sep 2007 02:17:20 -0700 (PDT) From: "Gordon Sim (JIRA)" <jenniferbrown@example.org> To: jenniferbrown@example.org Subject: [jira] Resolved: (QPID-561) c++ broker using incorrect value for xa-ok. In-Reply-To: <9965431.1188584358538.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/QPID-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-561. ----------------------------- Resolution: Fixed Fixed in rev 572264. > c++ broker using incorrect value for xa-ok. > ------------------------------------------- > > Key: QPID-561 > URL: https://issues.apache.org/jira/browse/QPID-561 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client, Java Client > Reporter: Alan Conway > > The qpidd broker uses the constant XA_OK=8, but the 0-10 XML defines xa-ok=0. The value 8 looks like a 0-9 throwback. > It appears that python uses the incorrect value also, since changing it to - broke the python xa tests with the broker. > constants.h now provides generated C++ constants for all AMQP constants define in XML, we should replace all hand-written constants with constants based on the generated ones. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 10:03:43 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 63108 invoked from network); 3 Sep 2007 10:03:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 10:03:42 -0000 Received: (qmail 83214 invoked by uid 500); 3 Sep 2007 10:03:37 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 83015 invoked by uid 500); 3 Sep 2007 10:03:37 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 82991 invoked by uid 99); 3 Sep 2007 10:03:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 03:03:37 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 10:04:51 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 5E2F871420B for <jenniferbrown@example.org>; Mon, 3 Sep 2007 03:03:19 -0700 (PDT) Message-ID: <9067754.1188813799383.JavaMail.jira@brutus> Date: Mon, 3 Sep 2007 03:03:19 -0700 (PDT) From: "Martin Ritchie (JIRA)" <jenniferbrown@example.org> To: jenniferbrown@example.org Subject: [jira] Updated: (QPID-554) Allow Hex view of object data messages In-Reply-To: <26534521.1187607810439.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/QPID-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie updated QPID-554: -------------------------------- Fix Version/s: (was: M2) M3 > Allow Hex view of object data messages > -------------------------------------- > > Key: QPID-554 > URL: https://issues.apache.org/jira/browse/QPID-554 > Project: Qpid > Issue Type: New Feature > Components: Java Management Console > Affects Versions: M2 > Reporter: Jia JIa > Assignee: Martin Ritchie > Priority: Minor > Fix For: M3 > > Attachments: mc-hexview-of-objmsg.zip, screenshot-1.jpg > > > Currently only text data is shown. Showing the first n bytes of the object msgs in hex would be helpful. Perhaps with the option to view the next n. > Similar code currently exists in the MessageStoreTool. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 10:03:44 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 63116 invoked from network); 3 Sep 2007 10:03:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 10:03:42 -0000 Received: (qmail 83225 invoked by uid 500); 3 Sep 2007 10:03:37 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 83017 invoked by uid 500); 3 Sep 2007 10:03:37 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 82990 invoked by uid 99); 3 Sep 2007 10:03:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 03:03:37 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 10:04:51 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 2D75271420A for <jenniferbrown@example.org>; Mon, 3 Sep 2007 03:03:19 -0700 (PDT) Message-ID: <21305716.1188813799149.JavaMail.jira@brutus> Date: Mon, 3 Sep 2007 03:03:19 -0700 (PDT) From: "Martin Ritchie (JIRA)" <jenniferbrown@example.org> To: jenniferbrown@example.org Subject: [jira] Resolved: (QPID-554) Allow Hex view of object data messages In-Reply-To: <26534521.1187607810439.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/QPID-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie resolved QPID-554. --------------------------------- Resolution: Fixed > Allow Hex view of object data messages > -------------------------------------- > > Key: QPID-554 > URL: https://issues.apache.org/jira/browse/QPID-554 > Project: Qpid > Issue Type: New Feature > Components: Java Management Console > Affects Versions: M2 > Reporter: Jia JIa > Assignee: Martin Ritchie > Priority: Minor > Fix For: M2 > > Attachments: mc-hexview-of-objmsg.zip, screenshot-1.jpg > > > Currently only text data is shown. Showing the first n bytes of the object msgs in hex would be helpful. Perhaps with the option to view the next n. > Similar code currently exists in the MessageStoreTool. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 13:36:07 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 47067 invoked from network); 3 Sep 2007 13:36:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 13:36:07 -0000 Received: (qmail 12908 invoked by uid 500); 3 Sep 2007 13:36:01 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 12887 invoked by uid 500); 3 Sep 2007 13:36:01 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 12878 invoked by uid 99); 3 Sep 2007 13:36:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 06:36:01 -0700 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jenniferbrown@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mx1.redhat.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 13:37:09 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [83.161.120.155]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l83DZZx8000666 for <jenniferbrown@example.org>; Mon, 3 Sep 2007 09:35:35 -0400 Received: from pobox.stuttgart.redhat.com (pobox.stuttgart.redhat.com [83.161.120.155]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l83DZYKd007726 for <jenniferbrown@example.org>; Mon, 3 Sep 2007 09:35:35 -0400 Received: from [83.161.120.155] (vpn-4-24.str.redhat.com [83.161.120.155]) by pobox.stuttgart.redhat.com (83.161.120.15560308/8.12.11) with ESMTP id l83DZXpM011100 for <jenniferbrown@example.org>; Mon, 3 Sep 2007 15:35:34 +0200 Subject: Re: M2 -> Trunk Merge Complete From: Arnaud Simon <jenniferbrown@example.org> Reply-To: jenniferbrown@example.org To: jenniferbrown@example.org In-Reply-To: <jenniferbrown@example.org> References: <jenniferbrown@example.org> <jenniferbrown@example.org> <jenniferbrown@example.org> Content-Type: text/plain Organization: Red Hat Date: Mon, 03 Sep 2007 15:35:17 +0200 Message-Id: <jenniferbrown@example.org> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Thu, 2007-08-30 at 11:06 -0400, Rafael Schloming wrote: > Robert Godfrey wrote: > > Thanks for your hard work on this Martin, > > > > much appreciated Huge +1 > > Arnaud is out for the week, but when he gets back I'll ask him to have a > look at the DTX issues and figure out what the deal is with store vs > messageStore. I am not that surprised that we had problems with merging M2 with the new dtx store. The dtx store fully replaces the previous store so I think that Martin did the right thing by rolling it back to use the M2 store. I have implemented three new stores really, a in-memory one, a JDBC one and a derby one. We need however to discuss the store interface during our F2F. This new store aims in providing support for dtx that is a 0.10 feature. So, unless we currently still have issues running some tests (in such a case I'll try to fix those issues) I would suggest that we make a decision regarding the new store during our F2F. I'll make a presentation about what I have done that could be a good starting point for a discussion. What do you think? Arnaud From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 14:37:23 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 64220 invoked from network); 3 Sep 2007 14:37:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 14:37:23 -0000 Received: (qmail 3356 invoked by uid 500); 3 Sep 2007 14:37:18 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 3252 invoked by uid 500); 3 Sep 2007 14:37:17 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 3243 invoked by uid 99); 3 Sep 2007 14:37:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 07:37:17 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jenniferbrown@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO nf-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 14:38:22 +0000 Received: by nf-out-0910.google.com with SMTP id h3so1279870nfh for <jenniferbrown@example.org>; Mon, 03 Sep 2007 07:36:50 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Noi+x1jQBCQ4btg1OTPkR99JmZ3aLAZ+gCBwz4yiIxVQLzGmat9RxrAs//L+C29MZOpChEFazlQEhOfi+EbeycoykLxWHAGUgUK0evrrbaU4+M17R5SUpg47tJfG3vaju8hycRdPZObry7uXVRqhz3TJDcjEaGMC1NwrhImzqhI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=tr1WVxkg5YnjCgwEiNfIcc1MHWrGijgfkEIuC4VolrNZFUHpPFqowQhks6chPxY4BwbCga6tyENgkGZRRtBF4+ilNPuP12uwnRW3s0wcmjdZX5rTI3/Tjp+i+4gFWKmDqiZ/o0OpdxB8aWiXJcDbHg5tLZLb14AkSmsdHnSWZmQ= Received: by 83.161.120.155 with SMTP id j9mr3304721huf.1188830210094; Mon, 03 Sep 2007 07:36:50 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Mon, 3 Sep 2007 07:36:44 -0700 (PDT) Message-ID: <jenniferbrown@example.org> Date: Mon, 3 Sep 2007 15:36:44 +0100 From: "Martin Ritchie" <jenniferbrown@example.org> Sender: jenniferbrown@example.org To: jenniferbrown@example.org, jenniferbrown@example.org Subject: Re: M2 -> Trunk Merge Complete In-Reply-To: <jenniferbrown@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <jenniferbrown@example.org> <jenniferbrown@example.org> <jenniferbrown@example.org> <jenniferbrown@example.org> X-Google-Sender-Auth: 94a8c15b36b42191 X-Virus-Checked: Checked by ClamAV on apache.org On 03/09/07, Arnaud Simon <jenniferbrown@example.org> wrote: > On Thu, 2007-08-30 at 11:06 -0400, Rafael Schloming wrote: > > Robert Godfrey wrote: > > > Thanks for your hard work on this Martin, > > > > > > much appreciated > > Huge +1 > > > > > Arnaud is out for the week, but when he gets back I'll ask him to have a > > look at the DTX issues and figure out what the deal is with store vs > > messageStore. > > I am not that surprised that we had problems with merging M2 with the > new dtx store. The dtx store fully replaces the previous store so I > think that Martin did the right thing by rolling it back to use the M2 > store. > I have implemented three new stores really, a in-memory one, a JDBC one > and a derby one. We need however to discuss the store interface during > our F2F. This new store aims in providing support for dtx that is a 0.10 > feature. > So, unless we currently still have issues running some tests (in such a > case I'll try to fix those issues) I would suggest that we make a > decision regarding the new store during our F2F. I'll make a > presentation about what I have done that could be a good starting point > for a discussion. > > What do you think? > > Arnaud Sounds good. What was surprising though was the similarity between the interfaces in store and the new messageStore interfaces. As I could see there wasn't any between the MessageStore interfaces other than the repackaging which was one of the minor issues with the merge. Was the 'store' package left for any particular reason after the creation of the messageStore package? I agree that we should discuss this at our F2F. Do we have any more concrete details on when this is going to be? Perhaps we need a thread to pull out the items we need to discuss. -- Martin Ritchie From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 15:29:03 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 10285 invoked from network); 3 Sep 2007 15:29:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 15:29:03 -0000 Received: (qmail 64217 invoked by uid 500); 3 Sep 2007 15:28:58 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 64187 invoked by uid 500); 3 Sep 2007 15:28:58 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 64174 invoked by uid 99); 3 Sep 2007 15:28:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 08:28:58 -0700 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jenniferbrown@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mx1.redhat.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 15:30:06 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [83.161.120.155]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l83FSVkd031114; Mon, 3 Sep 2007 11:28:31 -0400 Received: from pobox.stuttgart.redhat.com (pobox.stuttgart.redhat.com [83.161.120.155]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l83FSUxq013547; Mon, 3 Sep 2007 11:28:30 -0400 Received: from [83.161.120.155] (vpn-4-24.str.redhat.com [83.161.120.155]) by pobox.stuttgart.redhat.com (83.161.120.15560308/8.12.11) with ESMTP id l83FSTZD032751; Mon, 3 Sep 2007 17:28:29 +0200 Subject: Re: M2 -> Trunk Merge Complete From: Arnaud Simon <jenniferbrown@example.org> Reply-To: jenniferbrown@example.org To: Martin Ritchie <jenniferbrown@example.org> Cc: jenniferbrown@example.org In-Reply-To: <jenniferbrown@example.org> References: <jenniferbrown@example.org> <jenniferbrown@example.org> <jenniferbrown@example.org> <jenniferbrown@example.org> <jenniferbrown@example.org> Content-Type: text/plain Organization: Red Hat Date: Mon, 03 Sep 2007 17:28:05 +0200 Message-Id: <jenniferbrown@example.org> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Mon, 2007-09-03 at 15:36 +0100, Martin Ritchie wrote: > On 03/09/07, Arnaud Simon <jenniferbrown@example.org> wrote: > > On Thu, 2007-08-30 at 11:06 -0400, Rafael Schloming wrote: > > > Robert Godfrey wrote: > > > > Thanks for your hard work on this Martin, > > > > > > > > much appreciated > > > > Huge +1 > > > > > > > > Arnaud is out for the week, but when he gets back I'll ask him to have a > > > look at the DTX issues and figure out what the deal is with store vs > > > messageStore. > > > > I am not that surprised that we had problems with merging M2 with the > > new dtx store. The dtx store fully replaces the previous store so I > > think that Martin did the right thing by rolling it back to use the M2 > > store. > > I have implemented three new stores really, a in-memory one, a JDBC one > > and a derby one. We need however to discuss the store interface during > > our F2F. This new store aims in providing support for dtx that is a 0.10 > > feature. > > So, unless we currently still have issues running some tests (in such a > > case I'll try to fix those issues) I would suggest that we make a > > decision regarding the new store during our F2F. I'll make a > > presentation about what I have done that could be a good starting point > > for a discussion. > > > > What do you think? > > > > Arnaud > > Sounds good. What was surprising though was the similarity between the > interfaces in store and the new messageStore interfaces. As I could > see there wasn't any between the MessageStore interfaces other than > the repackaging which was one of the minor issues with the merge. Was > the 'store' package left for any particular reason after the creation > of the messageStore package? I agree that we should discuss this at > our F2F. I did not want to change everything I kept the old store and also plugged the new store that has a very different interface. > Do we have any more concrete details on when this is going to be? > Perhaps we need a thread to pull out the items we need to discuss. I guess that this may happen sometime in October. We still need to finalize that though. I am +1 for a thread for gathering the items we need to discuss. From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 15:47:52 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 40195 invoked from network); 3 Sep 2007 15:47:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 15:47:51 -0000 Received: (qmail 79611 invoked by uid 500); 3 Sep 2007 15:47:46 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 79585 invoked by uid 500); 3 Sep 2007 15:47:46 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 79572 invoked by uid 99); 3 Sep 2007 15:47:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 08:47:46 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jenniferbrown@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO rv-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 15:47:43 +0000 Received: by rv-out-0910.google.com with SMTP id k20so977682rvb for <jenniferbrown@example.org>; Mon, 03 Sep 2007 08:47:22 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ILie26oET3b978MzYXiCAMJt+UEe3RCVwu8HmZtGQyNuQExUMHIYS5TAI+s52Z/JCNg1ifGiFSWZ2pMI63TOoH2NnmObH7KjEWdAoGggDHQeL4ja28xvJM6dbUiGmW9X+MeWHjwIM1CN7FUhbEXvyuo+pqDjF367f72mScLSWuo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=oktYHoiY8upsIYsJKbqebGbcEkuOr15qR7cJc/Uc6zv4jl2tdok3PH2FtORx4w6P/Yhyprab053MoJ1Qp+m4lM84QOWdk6GRVES4p9mijiSr3Qp5NCGxoOsIDGxopnN3sdZCwCP3Itojk2t/Xmp9fPJiOa9ivgckmtFg0kZN+Aw= Received: by 83.161.120.155 with SMTP id p9mr2017716rvf.1188834442351; Mon, 03 Sep 2007 08:47:22 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Mon, 3 Sep 2007 08:47:22 -0700 (PDT) Message-ID: <jenniferbrown@example.org> Date: Mon, 3 Sep 2007 16:47:22 +0100 From: "Robert Greig" <jenniferbrown@example.org> To: jenniferbrown@example.org Subject: Building the C++ M2 branch MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org I decided to check out the M2 branch and try building the C++ from source. The platform was RH4 x86_64. The good news is that overall it worked very well, almost according to the instructions. When I am building, I am not root so I cannot use yum to update packages therefore everything needs to be available in non-standard locations. The only issues I had were: 1) Someone had installed an old version of boost in /usr/lib and this hadn't been built with -fPIC and therefore didn't link. I built my own version of boost, but its libraries had the compiler name at the end e.g. libboost_signals-gcc34.a. I therefore had to change the link lines to get it to link. I wasn't sure how to do this properly so I just hacked it in the Makefiles. Is there either a better way of building boost so it doesn't have these suffixes or a better way of configuring the libraries to link? 2) The build needed help2man installed. Unfortunately when I tried to install that, it needed some perl module (Local888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4gettext) and I had no idea how to install a perl module (and the package came with no instructions). Again I just hacked the makefile. Apart from those minor issues, it built and ran fine. RG From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 16:17:21 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 77394 invoked from network); 3 Sep 2007 16:17:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 16:17:21 -0000 Received: (qmail 12005 invoked by uid 500); 3 Sep 2007 16:17:16 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 11975 invoked by uid 500); 3 Sep 2007 16:17:16 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 11966 invoked by uid 99); 3 Sep 2007 16:17:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 09:17:15 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 16:18:31 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 02C02714208 for <jenniferbrown@example.org>; Mon, 3 Sep 2007 09:16:58 -0700 (PDT) Message-ID: <2903569.1188836218002.JavaMail.jira@brutus> Date: Mon, 3 Sep 2007 09:16:58 -0700 (PDT) From: "Robert Greig (JIRA)" <jenniferbrown@example.org> To: jenniferbrown@example.org Subject: [jira] Created: (QPID-562) Qpid C++ client appears to send heartbeats unnecessarily MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Qpid C++ client appears to send heartbeats unnecessarily -------------------------------------------------------- Key: QPID-562 URL: https://issues.apache.org/jira/browse/QPID-562 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: M2 Environment: RH4, x86_64, gcc 3.4.6 Reporter: Robert Greig Assignee: Gordon Sim Priority: Minor When running the topictest that comes with the C++ codebase, with -trace set, I see a lot of heartbeats being sent: SENT: Frame[channel=0; heartbeat] This is during periods of high activity where I do not expect to see them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 16:24:55 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 88500 invoked from network); 3 Sep 2007 16:24:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 16:24:51 -0000 Received: (qmail 19776 invoked by uid 500); 3 Sep 2007 16:24:46 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 19755 invoked by uid 500); 3 Sep 2007 16:24:45 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 19746 invoked by uid 99); 3 Sep 2007 16:24:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 09:24:45 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jenniferbrown@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO rv-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 16:24:42 +0000 Received: by rv-out-0910.google.com with SMTP id k20so983421rvb for <jenniferbrown@example.org>; Mon, 03 Sep 2007 09:24:21 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=uFm743TIDtN3RpfHk30F3FvI5LzirN3+mzh9VBftYphf57yU3/lasCHf93hIbjahoeHgPwZd7jx+m38vJqwwGUib3OV1F5ddKsGxS2BPeUZndVKGKtCKNbd5zaH8YZUKkubB1XSlFDrw/OiKldMocoqAKoEDkmyOV7IkWlXfi5I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=d6umH32n156AjYsJYrplmsfWh7izDadkW7+oJZla3AdUQmEj0f+2DeDnjDhg9+ins0xl/iUWVSQWgA8UYRaTI0JUXa/CDd1MmQbtSPoXQEF7A9o0wdsVcMKmosKyNMTi0MWmtJxOeJsfaZYTf5CSLeE9VBnEb0jQGc5KWqeN/X0= Received: by 83.161.120.155 with SMTP id h3mr2013606rvi.1188836661721; Mon, 03 Sep 2007 09:24:21 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Mon, 3 Sep 2007 09:24:21 -0700 (PDT) Message-ID: <jenniferbrown@example.org> Date: Mon, 3 Sep 2007 12:24:21 -0400 From: "Rajith Attapattu" <jenniferbrown@example.org> To: jenniferbrown@example.org Subject: Re: Building the C++ M2 branch In-Reply-To: <jenniferbrown@example.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_34002_15086503.1188836661706" References: <jenniferbrown@example.org> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_34002_15086503.1188836661706 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks for the feedback. I built it on an FC7 machine and only had to update a few. (of course I had root so yum was not a problem). The c++ team can better answer the other questions so I will leave it to them. Rajith On 9/3/07, Robert Greig <jenniferbrown@example.org> wrote: > > I decided to check out the M2 branch and try building the C++ from > source. The platform was RH4 x86_64. > > The good news is that overall it worked very well, almost according to > the instructions. When I am building, I am not root so I cannot use > yum to update packages therefore everything needs to be available in > non-standard locations. > > The only issues I had were: > > 1) Someone had installed an old version of boost in /usr/lib and this > hadn't been built with -fPIC and therefore didn't link. I built my own > version of boost, but its libraries had the compiler name at the end > e.g. libboost_signals-gcc34.a. I therefore had to change the link > lines to get it to link. I wasn't sure how to do this properly so I > just hacked it in the Makefiles. > > Is there either a better way of building boost so it doesn't have > these suffixes or a better way of configuring the libraries to link? > > 2) The build needed help2man installed. Unfortunately when I tried to > install that, it needed some perl module (Local888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4gettext) and I had > no idea how to install a perl module (and the package came with no > instructions). Again I just hacked the makefile. > > Apart from those minor issues, it built and ran fine. > > RG > ------=_Part_34002_15086503.1188836661706-- From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 22:07:32 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 38117 invoked from network); 3 Sep 2007 22:07:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 22:07:31 -0000 Received: (qmail 37028 invoked by uid 500); 3 Sep 2007 22:07:26 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 36998 invoked by uid 500); 3 Sep 2007 22:07:26 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 36989 invoked by uid 99); 3 Sep 2007 22:07:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 15:07:26 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jenniferbrown@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO rv-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 22:07:23 +0000 Received: by rv-out-0910.google.com with SMTP id k20so1039470rvb for <jenniferbrown@example.org>; Mon, 03 Sep 2007 15:07:03 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=srwCXe+Oh8q76H3Lokdu8fZg1b2JRtfi6Ch2OUX2c7INHA3IMBwowOBb9+9ZK4aMjeJXxkHqUoDqS8FS1ZrgLRRdIhSEcEiKHi/mv4MYQ3WLasFfBYdtZ+5rru6WcIdbMc2pt9rHkE8UBJtvDhfqWQORD7oRywZVGWhea6qUTmY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HWYcIaSO0HmhgC4s/O39/0S25jE3MBBU83M9EpLRU41o4v1qKV3Zfzqp91ePd3WCrdHHtycb1RBHDQ00LgfFG//0uMCbCSdegPuBK6oNHfC1ifKej5lomtGfL7u5rfEMXHW33u4mU87UNr13uDE32O+e+kU1gK3+buJ8Qo2k0do= Received: by 83.161.120.155 with SMTP id f12mr2133650rvq.1188857219858; Mon, 03 Sep 2007 15:06:59 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Mon, 3 Sep 2007 15:06:59 -0700 (PDT) Message-ID: <jenniferbrown@example.org> Date: Mon, 3 Sep 2007 23:06:59 +0100 From: "Robert Greig" <jenniferbrown@example.org> To: jenniferbrown@example.org Subject: Re: [ANN] java RC3 available In-Reply-To: <jenniferbrown@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <jenniferbrown@example.org> <jenniferbrown@example.org> <jenniferbrown@example.org> X-Virus-Checked: Checked by ClamAV on apache.org On 03/09/07, Martin Ritchie <jenniferbrown@example.org> wrote: > > 1. Why do we have separate access and jmxremote.access files? > The jmxremote.access file provides access controls for the JMX > management console. Not all users need be listed in this section. This > is purely a permission assignment. No authentication credentials are > inferred or granted through this file. See 3 below. > The access file serves as an example Access Control file for the basic > FileAccessManager. Currently only you my only restrict read access to > a particular virtualhost as performing the controls on write requires > a check on every publish method which will affect performance. When > AMQP has ACL/RBAC which I believe is planed for 0_11 then this will be > updated accordingly. I don't think I quite understand. Is the the access control file not a permission assignment - permission to connect to a virtual host? If so, how does it differ conceptually from jmxremote.access? > > Is it deliberate that there are no default values for those users in > > the passwd file? > > It is simply a case that no-one has updated all the authentication > password file to contain these users. OK I think this should be updated for M2.1 then, since for a new user it looks like something isn't quite right. > > 3. The etc directory is somewhat confusing for a new user (or even > > me!). We have the following "passwd" files: > > We have a number of different authentication modules each use a > different file format. > > > md5passwd > For use with Base64MD5PasswordFile. File contains Base64 encoded > hashes of the users password. > > > passwd > For use with PlainPasswordFile. File contains plain text passwords > > > passwdVhost > For use with PlainPasswordVhostFile. File contains plain text > passwords and additional Virtualhost authorisation details. Why are authorisation details contained with the user database? Can you put the same authorisation data into the MD5 file? > > 4. What is qpid-server.conf.jpp for? > > I believe this is some configuration file for JProfiler. It shouldn't > be in the broker etc directory, it that is the case. OK, we should remove it for M2.1 then. RG From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 22:20:06 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 40051 invoked from network); 3 Sep 2007 22:20:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 22:20:05 -0000 Received: (qmail 55291 invoked by uid 500); 3 Sep 2007 22:20:00 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 55260 invoked by uid 500); 3 Sep 2007 22:20:00 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 55251 invoked by uid 99); 3 Sep 2007 22:20:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 15:20:00 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jenniferbrown@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO rv-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 22:19:56 +0000 Received: by rv-out-0910.google.com with SMTP id k20so1041427rvb for <jenniferbrown@example.org>; Mon, 03 Sep 2007 15:19:36 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=nDsJyGJlukQcuCzUw8AkPpwO7PJspV6tqtsOaYJpglaVmqKFCma6LSQlw6K2o47XN4NuUaRz16jXaChNfhU25+uHbxzAhrUtNBG/V2zymtj1QzDDhvWy78TfgpjERVVPmBuCeb6Mfr33S6Fllc6IkuYXTB1va4zEj4yeyoP97cI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=QUWByWU2cyvY4EZkDQAfKrebkjCL+NZ6fiN1GZ35NeBOwbpsabVScxDlpijnZbjsyjgd3QUKriA9zSqDQ0jN5dOP4Ak10kjYuDjAFD6/2W7DwIdErVLHgh55f54iYm+kFHpCWCpNkCsrsmHpUGKl2vMbDkE1fM6SXXjonbxVCpo= Received: by 83.161.120.155 with SMTP id s19mr2133493rvi.1188857976192; Mon, 03 Sep 2007 15:19:36 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Mon, 3 Sep 2007 15:19:36 -0700 (PDT) Message-ID: <jenniferbrown@example.org> Date: Mon, 3 Sep 2007 23:19:36 +0100 From: "Robert Greig" <jenniferbrown@example.org> To: jenniferbrown@example.org Subject: C++ documentation MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Hi, Can someone let me know if there is any user documentation for the C++ broker or the C++ client? For example is there a guide to the broker, its features and the configuration options? Or any kind of API user guide? The following page is linked from the README in the distro but it hasn't been updated since February: http://cwiki.apache.org/confluence/pages/viewpage.action?pageId=28284 I think it badly needs updating. RG From qpid-dev-returnjenniferbrown@example.org Mon Sep 03 22:23:21 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 40578 invoked from network); 3 Sep 2007 22:23:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Sep 2007 22:23:21 -0000 Received: (qmail 56228 invoked by uid 500); 3 Sep 2007 22:23:16 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 56200 invoked by uid 500); 3 Sep 2007 22:23:15 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 56191 invoked by uid 99); 3 Sep 2007 22:23:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 15:23:15 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 22:24:31 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id EAAC1714163 for <jenniferbrown@example.org>; Mon, 3 Sep 2007 15:22:57 -0700 (PDT) Message-ID: <10450283.1188858177931.JavaMail.jira@brutus> Date: Mon, 3 Sep 2007 15:22:57 -0700 (PDT) From: "Robert Greig (JIRA)" <jenniferbrown@example.org> To: jenniferbrown@example.org Subject: [jira] Created: (QPID-563) [CPP broker] Printing out a hex address for each client connection is not helpful to end users MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [CPP broker] Printing out a hex address for each client connection is not helpful to end users ---------------------------------------------------------------------------------------------- Key: QPID-563 URL: https://issues.apache.org/jira/browse/QPID-563 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: M2 Environment: Any Reporter: Robert Greig Using the default out of the box configuration, the C++ broker prints to the console a hex address each time a client connects. To say this is lame is an understatement. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From qpid-dev-returnjenniferbrown@example.org Tue Sep 04 06:56:24 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 82323 invoked from network); 4 Sep 2007 06:56:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Sep 2007 06:56:23 -0000 Received: (qmail 75628 invoked by uid 500); 4 Sep 2007 06:56:18 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 75607 invoked by uid 500); 4 Sep 2007 06:56:18 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 75598 invoked by uid 99); 4 Sep 2007 06:56:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 23:56:18 -0700 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jenniferbrown@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mx1.redhat.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 06:57:28 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [83.161.120.155]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l846tpxB014012 for <jenniferbrown@example.org>; Tue, 4 Sep 2007 02:55:51 -0400 Received: from lacrosse.corp.redhat.com (lacrosse.corp.redhat.com [83.161.120.155]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l846tpqY031661 for <jenniferbrown@example.org>; Tue, 4 Sep 2007 02:55:51 -0400 Received: from [83.161.120.155] (vpn-4-56.str.redhat.com [83.161.120.155]) by lacrosse.corp.redhat.com (83.161.120.15560308/8.11.6) with ESMTP id l846toPm027884 for <jenniferbrown@example.org>; Tue, 4 Sep 2007 02:55:51 -0400 Message-ID: <jenniferbrown@example.org> Date: Tue, 04 Sep 2007 07:59:34 +0100 From: Gordon Sim <jenniferbrown@example.org> Organization: Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.,Registered in England and Wales under Company Registration No. 3798903,Directors: Michael Cunningham (USA), Charlie Peters (USA) and David Owens (Ireland) User-Agent: Thunderbird 83.161.120.155 (X11/20060501) MIME-Version: 1.0 To: jenniferbrown@example.org Subject: Re: C++ documentation References: <jenniferbrown@example.org> In-Reply-To: <jenniferbrown@example.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Robert Greig wrote: > Can someone let me know if there is any user documentation for the C++ > broker or the C++ client? > > For example is there a guide to the broker, its features and the > configuration options? Or any kind of API user guide? The broker will print a brief list of the recognised options when given the 'h/--help' flag and there is some doxygen generated documentation for the client API in docs/api/html. From qpid-dev-returnjenniferbrown@example.org Tue Sep 04 07:11:09 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 88067 invoked from network); 4 Sep 2007 07:11:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Sep 2007 07:11:08 -0000 Received: (qmail 87837 invoked by uid 500); 4 Sep 2007 07:11:03 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 87819 invoked by uid 500); 4 Sep 2007 07:11:02 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 87810 invoked by uid 99); 4 Sep 2007 07:11:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 00:11:02 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jenniferbrown@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO nf-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 07:10:55 +0000 Received: by nf-out-0910.google.com with SMTP id h3so1445756nfh for <jenniferbrown@example.org>; Tue, 04 Sep 2007 00:10:23 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=sE1i+ilT3jGU7i3U4cJMmXNbpPmkE/WVwmKWsSn2iwL51Yk8lo8jNmNeGo1MeVK4fs9p9z4Dv/9SAqf63nh8JF973BHE4qW2N1s+/0V1KMe+rD6gXtFIzn6iEB+eZZBR8Z4hcWSc9WuWM841PoHGBF8k2Gpjcka5hNL9sjfanZs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=jG+t1C6TYwkkBXoj+bbD4XCEef9A/EywoS/tho61v3yRfkGKd9RbD9tP27IdIEf4ZYUP64zLuEIbv9m8K+7jB0VO0qmSIbN7lbSkHDvRHpDicvHLLBoWNqQiBtjYlEDGE0V2z2hmU7mUseKOT2ZwlAqmZleWzUdif+3GdQRMRW8= Received: by 83.161.120.155 with SMTP id i15mr3803721huf.1188889822684; Tue, 04 Sep 2007 00:10:22 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Tue, 4 Sep 2007 00:10:22 -0700 (PDT) Message-ID: <jenniferbrown@example.org> Date: Tue, 4 Sep 2007 08:10:22 +0100 From: "Martin Ritchie" <jenniferbrown@example.org> Sender: jenniferbrown@example.org To: jenniferbrown@example.org Subject: Re: [ANN] java RC3 available In-Reply-To: <jenniferbrown@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <jenniferbrown@example.org> <jenniferbrown@example.org> <jenniferbrown@example.org> <jenniferbrown@example.org> X-Google-Sender-Auth: de17071ca05b8aaa X-Virus-Checked: Checked by ClamAV on apache.org On 03/09/07, Robert Greig <jenniferbrown@example.org> wrote: > On 03/09/07, Martin Ritchie <jenniferbrown@example.org> wrote: > > > > 1. Why do we have separate access and jmxremote.access files? > > The jmxremote.access file provides access controls for the JMX > > management console. Not all users need be listed in this section. This > > is purely a permission assignment. No authentication credentials are > > inferred or granted through this file. See 3 below. > > > The access file serves as an example Access Control file for the basic > > FileAccessManager. Currently only you my only restrict read access to > > a particular virtualhost as performing the controls on write requires > > a check on every publish method which will affect performance. When > > AMQP has ACL/RBAC which I believe is planed for 0_11 then this will be > > updated accordingly. > > I don't think I quite understand. Is the the access control file not a > permission assignment - permission to connect to a virtual host? If > so, how does it differ conceptually from jmxremote.access? The two files provide access to two different components they could be combined but that would then require a new file format. The jmxremote.access does not confer any permission to connect to the broker for sending messages only the level of management control that they have over the entire broker. The access file controls only connections for broker access, sending and receiving via a set virtualhost. You can think of it as access controls port 5672 and jmxremote.access controls 8999. > > > Is it deliberate that there are no default values for those users in > > > the passwd file? > > > > It is simply a case that no-one has updated all the authentication > > password file to contain these users. > > OK I think this should be updated for M2.1 then, since for a new user > it looks like something isn't quite right. agreed, though the management of users is definitely not recommended in the default Apache shipped Qpid. The credentials are sent in clear text across the wire. > > > 3. The etc directory is somewhat confusing for a new user (or even > > > me!). We have the following "passwd" files: > > > > We have a number of different authentication modules each use a > > different file format. > > > > > md5passwd > > For use with Base64MD5PasswordFile. File contains Base64 encoded > > hashes of the users password. > > > > > passwd > > For use with PlainPasswordFile. File contains plain text passwords > > > > > passwdVhost > > For use with PlainPasswordVhostFile. File contains plain text > > passwords and additional Virtualhost authorisation details. > > Why are authorisation details contained with the user database? Can > you put the same authorisation data into the MD5 file? They could be if you wrote a new PasswordFile class. I wrote the PlainPasswordVHostFile as a demonstration of how you could combine the PasswordFile and the AccessManager classes. The work on access control stopped after I made the simple demonstrator as we need to wait for the protocol WG to standardise the approach. The only alternative AccessManager classes available are AllowAll and DenyAll, which don't need any filesystem configuration. > > > 4. What is qpid-server.conf.jpp for? > > > > I believe this is some configuration file for JProfiler. It shouldn't > > be in the broker etc directory, it that is the case. > > OK, we should remove it for M2.1 then. Indeed looking at the etc directory there are a few files that probably shouldn't be there and certainly more documentation, around the files that are there would be good. > RG -- Martin Ritchie From qpid-dev-returnjenniferbrown@example.org Tue Sep 04 07:17:53 2007 Return-Path: <qpid-dev-returnjenniferbrown@example.org> Delivered-To: jenniferbrown@example.org Received: (qmail 89180 invoked from network); 4 Sep 2007 07:17:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Sep 2007 07:17:52 -0000 Received: (qmail 90946 invoked by uid 500); 4 Sep 2007 07:17:46 -0000 Delivered-To: jenniferbrown@example.org Received: (qmail 90915 invoked by uid 500); 4 Sep 2007 07:17:46 -0000 Mailing-List: contact jenniferbrown@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenniferbrown@example.org> List-Unsubscribe: <mailto:jenniferbrown@example.org> List-Post: <mailto:jenniferbrown@example.org> List-Id: <qpid-dev.incubator.apache.org> Reply-To: jenniferbrown@example.org Delivered-To: mailing list jenniferbrown@example.org Received: (qmail 90906 invoked by uid 99); 4 Sep 2007 07:17:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 00:17:46 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jenniferbrown@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO rv-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 07:17:42 +0000 Received: by rv-out-0910.google.com with SMTP id k20so1128549rvb for <jenniferbrown@example.org>; Tue, 04 Sep 2007 00:17:22 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=j14RsNtIUMKnAe9wHTzxq8rz7q0irOklCbKmGb54ZIsgN4+O7n5zNEN8U+TeeAEbhQpSHuIvzXT5kxGtqTt2W3jTsNjL19qq67RJhQR1y7LQbbrt+q3FUMwH0CVP+0wBGCvg5fywlLbvgg0In87RalNCoAoRg8jP2AhiYHCO7gY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sp6OIpZdQluIWb2bo4N/gja57jGtPuFIrd/cuemFYW4i7/3aStuUd4tfSmIhe0zB3vAYldFJGVEBmsNitEOR1AoAB25Kk6O8HO0WX3K5wLyw2nL7mcyzWtIoU8aLhj7RurjOa5fucoLBj30l903tYFyK7xa8DnOUD76YAJj3UtI= Received: by 83.161.120.155 with SMTP id j18mr2237458rvf.1188890242646; Tue, 04 Sep 2007 00:17:22 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Tue, 4 Sep 2007 00:17:22 -0700 (PDT) Message-ID: <jenniferbrown@example.org> Date: Tue, 4 Sep 2007 08:17:22 +0100 From: "Robert Greig" <jenniferbrown@example.org> To: jenniferbrown@example.org Subject: Re: [ANN] java RC3 available In-Reply-To: <jenniferbrown@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <jenniferbrown@example.org> <jenniferbrown@example.org> <jenniferbrown@example.org> <jenniferbrown@example.org> <jenniferbrown@example.org> X-Virus-Checked: Checked by ClamAV on apache.org On 04/09/07, Martin Ritchie <jenniferbrown@example.org> wrote: > The two files provide access to two different components they could be > combined but that would then require a new file format. The > jmxremote.access does not confer any permission to connect to the > broker for sending messages only the level of management control that > they have over the entire broker. The access file controls only > connections for broker access, sending and receiving via a set > virtualhost. You can think of it as access controls port 5672 and > jmxremote.access controls 8999. I definitely think they should be combined. I think that "authorisation" should be controlled in a single place to make it as simple as possible for the user. It seems to me that we ended up with two files for simplicity/speed of implementation rather than good design. > They could be if you wrote a new PasswordFile class. I wrote the > PlainPasswordVHostFile as a demonstration of how you could combine the > PasswordFile and the AccessManager
{'source': 'Apache Software Foundation Public Mail Archives'}