Re: build and post a windows binary
From our users list... does someone want to build the windows binary that we post as a use if you like basis. i.e. we make a volunteer builds section, and post builds based on a release as a service outside the release process. i.e. builds that people want and volunteer we post. thoughts? IMHO, Windows binary distribution is an integral part of the release process. Danushka -- Danushka Menikkumbura Technical Lead, WSO2 Inc. blog : http://danushka-menikkumbura.blogspot.com/ http://wso2.com/ - "The Open Source SOA Company" - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
site export
If the site looks weird, I am hacking on the auto export with help from Jonathan so far to try get it to look better, hold off on comments... I'll solicit feedback once I think progress has been made. Carl. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
build and post a windows binary
From our users list... does someone want to build the windows binary that we post as a use if you like basis. i.e. we make a volunteer builds section, and post builds based on a release as a service outside the release process. i.e. builds that people want and volunteer we post. thoughts? Carl. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
Hi all, Here's a summary of all the proposed slogans.. Apache Qpid: Open Source AMQP Messaging Apache Qpid: Fast, Reliable, AMQP Messaging Apache Qpid: AMQP Messaging from Point A to B in 10 microseconds or less! Apache Qpid: *The* AMQP Implementation Apache Qpid: Advanced Messaging, Quick, Purposeful Apache Qpid, Enterprise Messaging through AMQP Apache Qpid, AMQP Enterprise Messaging Apache Qpid - Fast, Reliable, Interoperable Enterprise Messaging Apache Qpid - The Open Source AMQP Implementation Keep on proposing I just wanted to summarize it to compare all of them. Lahiru On Thu, Jan 22, 2009 at 10:20 AM, Carl Trieloff wrote: > > >> 2. We do express the fact that Qpid is an AMQP implementation. In which >> case, the slogan should express the fact that we do it wright. Therefore, >> something like >> "Apache Qpid - The Open Source AMQP Implementation" sounds good. >> > > > this one > > Carl. > > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > -- Apache Qpid, Worlds dominant messaging middleware..!!!
[jira] Resolved: (QPID-1611) queue durability is lost on broker-newbie sync.
[ https://issues.apache.org/jira/browse/QPID-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-1611. -- Resolution: Fixed Fix Version/s: M5 Committed as r736814 > queue durability is lost on broker-newbie sync. > --- > > Key: QPID-1611 > URL: https://issues.apache.org/jira/browse/QPID-1611 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: michael j. goulish >Priority: Critical > Fix For: M5 > > Attachments: 480871.diff > > > queue durability does not survive cluster broker newbie sync. > When a new broker is syncing up with a cluster, it gets all the information > it needs to preserve queue durability, > But the code pathway that we go through in that case does not tell the > journaling code to create a journal. > This has the effect of making the queue not durable after all. > ! catch attached patch ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Draft Announcement for M4
Carl Trieloff wrote: Here are some more items that can be sorted in from the wiki * .NET, WCF and excel support for AMQP 0-10 * SSL added for C++ broker and all clients * Windows port for C++ client & broker * Solaris port for C++ client & broker I believe there is still some work outstanding on the solaris port. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1611) queue durability is lost on broker-newbie sync.
[ https://issues.apache.org/jira/browse/QPID-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael j. goulish updated QPID-1611: - Description: queue durability does not survive cluster broker newbie sync. When a new broker is syncing up with a cluster, it gets all the information it needs to preserve queue durability, But the code pathway that we go through in that case does not tell the journaling code to create a journal. This has the effect of making the queue not durable after all. ! catch attached patch ! was: BZ 480871 queue durability does not survive cluster broker newbie sync. ! catch attached patch ! Summary: queue durability is lost on broker-newbie sync. (was: patch for BZ 480871) > queue durability is lost on broker-newbie sync. > --- > > Key: QPID-1611 > URL: https://issues.apache.org/jira/browse/QPID-1611 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: michael j. goulish >Priority: Critical > Attachments: 480871.diff > > > queue durability does not survive cluster broker newbie sync. > When a new broker is syncing up with a cluster, it gets all the information > it needs to preserve queue durability, > But the code pathway that we go through in that case does not tell the > journaling code to create a journal. > This has the effect of making the queue not durable after all. > ! catch attached patch ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1611) patch for BZ 480871
[ https://issues.apache.org/jira/browse/QPID-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael j. goulish updated QPID-1611: - Attachment: 480871.diff > patch for BZ 480871 > --- > > Key: QPID-1611 > URL: https://issues.apache.org/jira/browse/QPID-1611 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: michael j. goulish >Priority: Critical > Attachments: 480871.diff > > > BZ 480871 > queue durability does not survive cluster broker newbie sync. > ! catch attached patch ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-1611) patch for BZ 480871
patch for BZ 480871 --- Key: QPID-1611 URL: https://issues.apache.org/jira/browse/QPID-1611 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: michael j. goulish Priority: Critical BZ 480871 queue durability does not survive cluster broker newbie sync. ! catch attached patch ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1507) Connect and Cancel Buttons don't display on Mac OS X builds
[ https://issues.apache.org/jira/browse/QPID-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666289#action_12666289 ] Robert Gemmell commented on QPID-1507: -- This was resolved through QPID-1010 > Connect and Cancel Buttons don't display on Mac OS X builds > --- > > Key: QPID-1507 > URL: https://issues.apache.org/jira/browse/QPID-1507 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Reporter: Martin Ritchie >Priority: Critical > > Summary: > As the 'Connect' and 'Cancel' buttons are not displayed on the Mac OS X Build > of the JMX Management Console it is not possible to connect to a broker. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1509) Buttons are often missing their text on Linux build.
[ https://issues.apache.org/jira/browse/QPID-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666288#action_12666288 ] Robert Gemmell commented on QPID-1509: -- This was resolved through QPID-1010 > Buttons are often missing their text on Linux build. > > > Key: QPID-1509 > URL: https://issues.apache.org/jira/browse/QPID-1509 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Reporter: Martin Ritchie > > Summary: > When running under RHEL4 the JMX Management console often loses the text on > the buttons. This will make it difficult for new users to know which button > is 'Connect' and which 'Cancel'. > This is a transient issue and restarting will often bring the text back. But > I see no pattern to what might cause the text to disappear. > I see this as I have a local settings file. > Start the JMX Console > Select a connection from my list > Click Reconnect > Buttons often don't show 'Connect' / 'Cancel' but as they are ~ 12px high I > can still click and tab to them. Unlike Mac OS X build that doesn't show the > buttons at all (QPID-1507) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1241) qpidmc.bat script does not cope with spaces (" ") in the path.
[
https://issues.apache.org/jira/browse/QPID-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666287#action_12666287
]
Robert Gemmell commented on QPID-1241:
--
In addition to the fix put in place in the batch script with the above patch,
QPID-1592 has resolves this by removing the batch script completely and relying
on the Eclipse RCP executable to directly launch the MC.
> qpidmc.bat script does not cope with spaces (" ") in the path.
> --
>
> Key: QPID-1241
> URL: https://issues.apache.org/jira/browse/QPID-1241
> Project: Qpid
> Issue Type: Bug
> Components: Java Management : JMX Console
>Affects Versions: M2, M2.1, M3
>Reporter: Martin Ritchie
>Assignee: Marnie McCormack
> Attachments: QPID-1241_23nov2008.patch
>
>
> Summary:
> The management console cannot be installed in to "Program Files" as
> qpidmc.bat script does not correctly operate due to the space in the path.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1510) Splash Screen does not go away on Windows build
[ https://issues.apache.org/jira/browse/QPID-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666285#action_12666285 ] Robert Gemmell commented on QPID-1510: -- QPID-1592 resolves this issue. > Splash Screen does not go away on Windows build > --- > > Key: QPID-1510 > URL: https://issues.apache.org/jira/browse/QPID-1510 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console, Starter >Reporter: Martin Ritchie >Priority: Minor > > Summary: > The new builds of the Windows console display the splash screen but do not > remove it when the console has started. > Perhaps the units of -splashScreen 600 have changed. > The window is not set to be the front most window so other apps can be moved > in front of it but if you had a small window right at the centre of your > screen you would have to quite the console to find it again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1508) Splash Screen is not displayed on Mac OS X/Linux Builds
[ https://issues.apache.org/jira/browse/QPID-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666281#action_12666281 ] Robert Gemmell commented on QPID-1508: -- QPID-1592 resolves this issue > Splash Screen is not displayed on Mac OS X/Linux Builds > --- > > Key: QPID-1508 > URL: https://issues.apache.org/jira/browse/QPID-1508 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Reporter: Martin Ritchie > > Summary: > There must be a configuration mistake somewhere as the splash screen is not > shown in the Mac OS X or Linux Builds of the JMX Console -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Draft Announcement for M4
QPID-957 and QPID-1334 are the same thing, the JMX CLI. -Original Message- From: Rafael Schloming [mailto:rafa...@redhat.com] Sent: 22 January 2009 19:26 To: dev@qpid.apache.org Subject: Draft Announcement for M4[MESSAGE NOT SCANNED] I've mined the features section from the JIRA release notes, but stuff not in JIRA may have been overlooked, so please review and comment. --Rafael - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Draft Announcement for M4
Here are some more items that can be sorted in from the wiki * .NET, WCF and excel support for AMQP 0-10 * SSL added for C++ broker and all clients * Windows port for C++ client & broker * Solaris port for C++ client & broker * C++ Broker o ACL o Active-Active clustering o Federation, push bridges & dynamic routes o RDMA for C++ broker & C++ client (70-80us, yes us max latency on a well setup machines) o support for message TTL o Queue options + added RING/ STRICT ring + LVQ o Exchange options + LVE + message sequencing o XQuery based XML Exchange now as plugin * Performance work * Management for AMQP 0-10 o QMF C updates + Python + C++ o QMF Agent + C++ o QMan JMX bridge for QMF o Alerts/ logger for QMF events * JMSXUserId * Java broker o Message Priority o bug fixes o some prep work for AMQP 0-10 Rafael Schloming wrote: I've mined the features section from the JIRA release notes, but stuff not in JIRA may have been overlooked, so please review and comment. --Rafael - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Draft Announcement for M4
I've mined the features section from the JIRA release notes, but stuff not in JIRA may have been overlooked, so please review and comment. --Rafael The Apache Qpid community is pleased to announce the release of Apache Qpid M4! Apache Qpid is a cross platform enterprise messaging solution which implements the Advanced Message Queueing Protocol (http://www.amqp.org). It provides brokers written in Java and C++ and clients in C++, Java (including a JMS implementation), .Net, Python, and Ruby. New features included in this release are: [QPID-106] - SSL for C++ broker [QPID-107] - ACL and RBAC [QPID-528] - Support message ttl [QPID-957] - CLI for extract information from Apache Qpid Java broker [QPID-1174] - Remote Management Agent for management of external components [QPID-1209] - Port to Windows [QPID-1248] - Add "last image caching" so a new subscriber immediately gets the most recently sent msg [QPID-1277] - .net AMQP 0.10 support [QPID-1279] - Application level status communication [QPID-1281] - .Net WCF support (0.10) [QPID-1288] - Python API for Management Console Access [QPID-1290] - Add ability to move messages from one queue to another [QPID-1293] - .net Excel Add In [QPID-1296] - Add SSL support to java client [QPID-1297] - Add ACL support for federation [QPID-1334] - JMX Management Console for Qpid Java broker [QPID-1339] - failover and replay for the 0-10 java client [QPID-1348] - Dynamic binding for federation links [QPID-1349] - Push routing for Federation [QPID-1366] - C++ Broker Federation - Automatic configuration of anti-looping It is available to download from: http://www.apache.org/dist/qpid/M4/ Complete release notes are available here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&styleName=Html&version=12313279 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
2. We do express the fact that Qpid is an AMQP implementation. In which case, the slogan should express the fact that we do it wright. Therefore, something like "Apache Qpid - The Open Source AMQP Implementation" sounds good. this one Carl. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
I think something that close to something that is all over google as linked to a direct competitor is a Really Bad Idea. +1. I think we have two options here. 1. We never say that Qpid is an AMQP implementation. In which case, the slogan should express some key attributes of AMQP. Therefore something like "Apache Qpid - Fast, Reliable, Interoperable Enterprise Messaging" would be nice. 2. We do express the fact that Qpid is an AMQP implementation. In which case, the slogan should express the fact that we do it wright. Therefore, something like "Apache Qpid - The Open Source AMQP Implementation" sounds good. Danushka -- Danushka Menikkumbura Technical Lead, WSO2 Inc. blog : http://danushka-menikkumbura.blogspot.com/ http://wso2.com/ - "The Open Source SOA Company" - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1242) Ability to view Binary Messages was lost in the merge
[ https://issues.apache.org/jira/browse/QPID-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell updated QPID-1242: - Attachment: QPID-1242_22jan2009.patch org.apache.commons.codec_1.3.0.v20080530-1600.jar The attached patch reintegrates the previous source changes from r571491 which were lost during merge, with a modification made to remove the line asciiText.setTopIndex(hexText.getTopIndex()); below line 603 and comparable command after line 608 that would prevent the scrollbars from moving concurrently, forcing them to stay at their topmost position at all times. The relevant configuration changes to the MC build were made in accordance with the new build system/layout. The attached commons-codec rcp plugin should be placed in qpid/java/lib > Ability to view Binary Messages was lost in the merge > - > > Key: QPID-1242 > URL: https://issues.apache.org/jira/browse/QPID-1242 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Affects Versions: M2, M2.1, M3 >Reporter: Martin Ritchie > Attachments: org.apache.commons.codec_1.3.0.v20080530-1600.jar, > QPID-1242_22jan2009.patch > > > Summary: > The ability to view binary messages (ascii and hex views) were lost when the > M2.x code base was merged to trunk. > It was checked in at r571491 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1030) Making JMS easier for users
[ https://issues.apache.org/jira/browse/QPID-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-1030. Resolution: Duplicate This issue is also covered by QPID-1308 > Making JMS easier for users > --- > > Key: QPID-1030 > URL: https://issues.apache.org/jira/browse/QPID-1030 > Project: Qpid > Issue Type: Improvement > Components: Java Client >Affects Versions: M3 >Reporter: Arnaud Simon >Assignee: Rajith Attapattu > Fix For: M4 > > > This Jira is related to the mailing list thread: "Making JMS easier for > users" (Note: I haven't found one related to this thread, please just mark > that issue as duplicated if one already exists) > Issue, when we setup JMS topics is that it creates a tmp queue for each > connection with an ugly name. This makes it hard for admins to map the temp > queues to the topics. > It has been decided that the following scheme should be used: > @_ > where > is a 36 character UUID string produced (for example) by > java.util.randomUUID().toString() > is a maximum of 207 single-byte characters from the > binding key used. > is as many characters as possible from the name of the > exchange while still fitting into a 255 character queue-name. > this would give queue names like > stocks.nys...@amq.direct_47c1b90d-2eb6-4245-a0e2-e07c2547bf7d -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1308) JMS Temprory Queue naming
[
https://issues.apache.org/jira/browse/QPID-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-1308:
---
Affects Version/s: (was: M4)
> JMS Temprory Queue naming
> -
>
> Key: QPID-1308
> URL: https://issues.apache.org/jira/browse/QPID-1308
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
>Reporter: Rajith Attapattu
>Assignee: Rajith Attapattu
> Attachments: temp_queue_naming.patch
>
>
> The following is a proposal for temp queue naming.
> Currently our temp queue naming is hard coded to "Temp_ " + uuid.
> We could change this to a format that is configurable and captures more
> useful information that can be utilized by,
> a) management tools to provide more visibility
> b) ACL modules.
> I propose the following format
> {host}.{port}.{user_prefix}.{uuid}.
> The above format is configurable with {uuid} being the only mandatory part.
> The order of the tokens could also be changed.
> The scheme can be set globally using a jvm argument or per connection using
> connection URL.
> Example.
> {user_prefix}_{uuid} = Temp_535fewfsgdsg where user_prefix = "Temp"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1030) Making JMS easier for users
[ https://issues.apache.org/jira/browse/QPID-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-1030: --- Status: Open (was: Ready To Review) This is also covered by QPID-1308 > Making JMS easier for users > --- > > Key: QPID-1030 > URL: https://issues.apache.org/jira/browse/QPID-1030 > Project: Qpid > Issue Type: Improvement > Components: Java Client >Affects Versions: M3 >Reporter: Arnaud Simon >Assignee: Rajith Attapattu > Fix For: M4 > > > This Jira is related to the mailing list thread: "Making JMS easier for > users" (Note: I haven't found one related to this thread, please just mark > that issue as duplicated if one already exists) > Issue, when we setup JMS topics is that it creates a tmp queue for each > connection with an ugly name. This makes it hard for admins to map the temp > queues to the topics. > It has been decided that the following scheme should be used: > @_ > where > is a 36 character UUID string produced (for example) by > java.util.randomUUID().toString() > is a maximum of 207 single-byte characters from the > binding key used. > is as many characters as possible from the name of the > exchange while still fitting into a 255 character queue-name. > this would give queue names like > stocks.nys...@amq.direct_47c1b90d-2eb6-4245-a0e2-e07c2547bf7d -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-739) When using an AMQP destination, the queue routing key is not set correctly
[ https://issues.apache.org/jira/browse/QPID-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-739. --- Resolution: Won't Fix See https://issues.apache.org/jira/browse/QPID-741 for more details. > When using an AMQP destination, the queue routing key is not set correctly > --- > > Key: QPID-739 > URL: https://issues.apache.org/jira/browse/QPID-739 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: M3 >Reporter: Arnaud Simon >Assignee: Rajith Attapattu > Fix For: M4 > > > When a destination is looked up from JNDI, the queue name is used as routing > key when it should be the destination name. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-741) The BindingURL format is incorrect
[ https://issues.apache.org/jira/browse/QPID-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-741. --- Resolution: Won't Fix The destination is used in DurableTopicSubscriptions. It is best to address any issues when we look at refactoring the BindingURL alltogether. Currently there are several aspects that cannot be sucessfully handled via the current binding URL. > The BindingURL format is incorrect > -- > > Key: QPID-741 > URL: https://issues.apache.org/jira/browse/QPID-741 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: M3 >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu > Fix For: M4 > > > The binding URL is defined as follows. > :///[]/[]?=''[,='']* > RoutingKey is given as a valid option (See BindingURL class) and the > following documentation http://cwiki.apache.org/qpid/bindingurlformat.html. > Then in AMQDestination we see that the constructors has a field called > "destinationName" (in addition to exchangeName). > As per the AMQP spec, destination refers to the exchange you are publishing. > Therefore the binding url format is incorrect, as destination has no meaning > in the URL. > It cannot be the routing_key as it is given as a valid option. So I propose > we get rid of it. > However the documentation here is correct, but sadly not reflected in the > code properly. > http://cwiki.apache.org/qpid/bindingurlformat.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Question about a warning (and comment about the warning)
cpp/src/qpid/sys/posix/LockFile.cpp, line 59 throws a warning when built with g++ 4.3. Here is the compiler output: g++ -DHAVE_CONFIG_H -I. -Igen -I./gen -Werror -pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wvolatile-register-var -Winvalid-pch -Wno-system-headers -Woverloaded-virtual -g -O2 -MT qpid/sys/posix/LockFile.lo -MD -MP -MF qpid/sys/posix/.deps/LockFile.Tpo -c qpid/sys/posix/LockFile.cpp -fPIC -DPIC -o qpid/sys/posix/.libs/LockFile.o cc1plus: warnings being treated as errors qpid/sys/posix/LockFile.cpp: In destructor 'qpid::sys::LockFile::~LockFile()': qpid/sys/posix/LockFile.cpp:59: error: ignoring return value of 'int lockf(int, int, __off_t)', declared with attribute warn_unused_result qpid/sys/posix/LockFile.cpp: In destructor 'qpid::sys::LockFile::~LockFile()': qpid/sys/posix/LockFile.cpp:59: error: ignoring return value of 'int lockf(int, int, __off_t)', declared with attribute warn_unused_result qpid/sys/posix/LockFile.cpp: In destructor 'qpid::sys::LockFile::~LockFile()': qpid/sys/posix/LockFile.cpp:59: error: ignoring return value of 'int lockf(int, int, __off_t)', declared with attribute warn_unused_result Here is the line in question: (void) ::lockf(f, F_ULOCK, 0); // Suppress warnings about ignoring return value. What seems a bit odd is that, as you can see, there is a comment about trying to suppress that warning, but it obviously isn't working anymore. Changing the line to: int ret; ret = ::lockf(f, F_ULOCK, 0); // Suppress warnings about ignoring return value. Does make the error go away, although it is a bit inelegant to get ret and then not actually check if for an error condition. In several other locations there are write calls where the return value is not handled, which also upsets G++ 4.3. I can send a patch of what I changed if that would help. I'm also flipping through Jira to see if it looks appropriate to try and make an entry there. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1583) IP White/Black lists for virtual hosts
[ https://issues.apache.org/jira/browse/QPID-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666194#action_12666194 ] Aidan Skinner commented on QPID-1583: - OK, a simpler approach which aovids problems with rule precedence could be adding a element to the config file. Elements inside would be or . would read the file specified at path, which would contain an . would validate it's hostname against the host attribute and cause a fatal error on startup if it did not match. would contain further entries, but not . would have action, virtualhost, hostname and network attributes. Action and one of host or network would be mandatory. Virtualhost would be optional, if specified it would match one of the virtualhosts. The action attribute would be either allow or deny. host would be a regexp against which it would match the reverse dns lookup of the connecting IP. network would be a CIDR against which the IP would be matched. The first which matched the connection would apply. If no rules applied, the default-action would apply. Example: any machine in the qpid.apache.org domain could access dev. Any machine in the 192.168.1.0/24 network would be allowed access to any virtualhost other than prod Any machine in the 10.0.0.0/8 network would be allowed access to any virtual host Any other machine would be denied access. > IP White/Black lists for virtual hosts > -- > > Key: QPID-1583 > URL: https://issues.apache.org/jira/browse/QPID-1583 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: M5 >Reporter: Aidan Skinner >Assignee: Aidan Skinner > Fix For: M5 > > > Having white/black lists for connecting to a virtual host would be useful. > Questions: > - need to provide an easy way for operate to maintain, secure & backup this > list > - should consider what to do if there file/props etc for this are > corrupt/format wrong > - if possible, the security filtering this provides should be part of a > potential chain of access REDUCING plugins so that this is easy to drop in > and teams can potentially write their own reducing filter class and use > abstraction to define in config for broker > - needs to be at vhost level, and potentially at queue level ? > > Explicit allow/deny lists of connection patterns on virtualhosts in > config.xml, existing ACL infrastructure for entities below that. > Pattern would be one of: > IP address > CIDR mask > regexp on hostname > Changes would not be possible while broker was running, the file would need > to be editted and then the broker restarted. This avoids the necessity to > consider what happens to existing connections which would be excluded by a > new rule. Errors in configuration would prevent broker startup. > Implementation wise, a new IPRestriction class would extend ACLPlugin which > listens for ConnectionOpen and checks against the list of rules. > AMQProtocolSession needs to expose access to the underlying socket. > --- > We may need to reconsider allowing changes to the lists while the broker is > running. It would probably imply storing these outwith the main configuration > file and instead having something else, potentially a properties file, which > could be editted by the broker as it runs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
On Thu, Jan 22, 2009 at 4:13 PM, Rajith Attapattu wrote: > On Thu, Jan 22, 2009 at 10:11 AM, Aidan Skinner > wrote: > >> On Thu, Jan 22, 2009 at 3:00 PM, Carl Trieloff >> wrote: >> > Lahiru Gunathilake wrote: >> >> >> >> On Thu, Jan 22, 2009 at 6:57 AM, Marnie McCormack < >> >> marnie.mccorm...@googlemail.com> wrote: >> >> >> >> >> >>> >> >>> Apache Qpid, Enterprise Messaging through AMQP >> > >> > >> > Apache Qpid, AMQP Enterprise Messaging that just works. >> >> It's pretty similar to the title of RabbitMQ's tech talk: >> http://www.rabbitmq.com/resources/google-tech-talk-final/google.html >> > > Yes this slogan seems good to me. +1 I think something that close to something that is all over google as linked to a direct competitor is a Really Bad Idea. - Aidan -- Apache Qpid - World Domination through Advanced Message Queueing http://qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
On Thu, Jan 22, 2009 at 10:11 AM, Aidan Skinner wrote: > On Thu, Jan 22, 2009 at 3:00 PM, Carl Trieloff > wrote: > > Lahiru Gunathilake wrote: > >> > >> On Thu, Jan 22, 2009 at 6:57 AM, Marnie McCormack < > >> marnie.mccorm...@googlemail.com> wrote: > >> > >> > >>> > >>> Apache Qpid, Enterprise Messaging through AMQP > > > > > > Apache Qpid, AMQP Enterprise Messaging that just works. > > It's pretty similar to the title of RabbitMQ's tech talk: > http://www.rabbitmq.com/resources/google-tech-talk-final/google.html > Yes this slogan seems good to me. +1 > > - Aidan > > -- > Apache Qpid - World Domination through Advanced Message Queueing > http://qpid.apache.org > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/
[jira] Closed: (QPID-1584) [Java] Provide VirtualHost level ACL permission
[ https://issues.apache.org/jira/browse/QPID-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie closed QPID-1584. Resolution: Duplicate > [Java] Provide VirtualHost level ACL permission > --- > > Key: QPID-1584 > URL: https://issues.apache.org/jira/browse/QPID-1584 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Reporter: Marnie McCormack >Assignee: Martin Ritchie > Fix For: M5 > > > Prior to introduction of ACLs in current format, it was possible to define > permissions for an entire virtual host on a user basis. This is a useful > feature, which was lost with new ACLs. There should be a way to provide > permissions across all artifacts in a vh for a given user. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1304) SimpleACL is unable to provide virtualhost level access control for a given user
[ https://issues.apache.org/jira/browse/QPID-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie updated QPID-1304: - Description: The removal of the VHostPassword file in favour of the new ACL format has lost the ability to limit access per virtualhost. It should be possible to define permissions for an entire virtual host on a user basis.There should be a way to provide permissions across all artifacts in a vh for a given user. We need to implement the section in the XML ACL file to restore the functionality that was present with the VHost PrincipalDatabase. was: The change in structure and removal of the VHostPassword file in favour of the new ACL format has lost the ability to limit access per virtualhost. We need to implement the section in the XML ACL file to restore the functionality that was present with the VHost PrincipalDatabase. Summary: SimpleACL is unable to provide virtualhost level access control for a given user (was: ACLPlugin change has removed VHostPassword file plugin.) > SimpleACL is unable to provide virtualhost level access control for a given > user > > > Key: QPID-1304 > URL: https://issues.apache.org/jira/browse/QPID-1304 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: M2.1, M3 >Reporter: Martin Ritchie >Assignee: Martin Ritchie > Fix For: M5 > > > The removal of the VHostPassword file in favour of the new ACL format has > lost the ability to limit access per virtualhost. It should be possible to > define permissions for an entire virtual host on a user basis.There should be > a way to provide permissions across all artifacts in a vh for a given user. > We need to implement the section in the XML ACL file to restore the > functionality that was present with the VHost PrincipalDatabase. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1583) IP White/Black lists for virtual hosts
[ https://issues.apache.org/jira/browse/QPID-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666170#action_12666170 ] Aidan Skinner commented on QPID-1583: - Knowing about all brokers on the server is kind of hard, they could all share the same file though. We could allow multiple files to be specified in the config file so you could have one for the server and one for the specific broker. > IP White/Black lists for virtual hosts > -- > > Key: QPID-1583 > URL: https://issues.apache.org/jira/browse/QPID-1583 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: M5 >Reporter: Aidan Skinner >Assignee: Aidan Skinner > Fix For: M5 > > > Having white/black lists for connecting to a virtual host would be useful. > Questions: > - need to provide an easy way for operate to maintain, secure & backup this > list > - should consider what to do if there file/props etc for this are > corrupt/format wrong > - if possible, the security filtering this provides should be part of a > potential chain of access REDUCING plugins so that this is easy to drop in > and teams can potentially write their own reducing filter class and use > abstraction to define in config for broker > - needs to be at vhost level, and potentially at queue level ? > > Explicit allow/deny lists of connection patterns on virtualhosts in > config.xml, existing ACL infrastructure for entities below that. > Pattern would be one of: > IP address > CIDR mask > regexp on hostname > Changes would not be possible while broker was running, the file would need > to be editted and then the broker restarted. This avoids the necessity to > consider what happens to existing connections which would be excluded by a > new rule. Errors in configuration would prevent broker startup. > Implementation wise, a new IPRestriction class would extend ACLPlugin which > listens for ConnectionOpen and checks against the list of rules. > AMQProtocolSession needs to expose access to the underlying socket. > --- > We may need to reconsider allowing changes to the lists while the broker is > running. It would probably imply storing these outwith the main configuration > file and instead having something else, potentially a properties file, which > could be editted by the broker as it runs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1587) Add java LVQ samples
[ https://issues.apache.org/jira/browse/QPID-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666166#action_12666166 ] Marnie McCormack commented on QPID-1587: Are there commits for this JIRA - they don't seem to be showing up ? Thanks. > Add java LVQ samples > > > Key: QPID-1587 > URL: https://issues.apache.org/jira/browse/QPID-1587 > Project: Qpid > Issue Type: Improvement > Components: Java Client >Affects Versions: M5 >Reporter: Arnaud Simon >Assignee: Arnaud Simon > Fix For: M5 > > > It would nice to show how a Java client can handle LVQ. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1583) IP White/Black lists for virtual hosts
[ https://issues.apache.org/jira/browse/QPID-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666165#action_12666165 ] Marnie McCormack commented on QPID-1583: The whitelist should not be in the virtual hosts file as I think it likely that these config details may be owned by different teams. It should also be possible to specify an IP address once in the config and apply it to a) all brokers on this server b) all vhs on this broker c) ultimately all brokers in this cluster etc. Commons config will sort out the listening for updates out of the box, so no need to introduce anything new from that pov (http://commons.apache.org/configuration/userguide/howto_events.html) > IP White/Black lists for virtual hosts > -- > > Key: QPID-1583 > URL: https://issues.apache.org/jira/browse/QPID-1583 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: M5 >Reporter: Aidan Skinner >Assignee: Aidan Skinner > Fix For: M5 > > > Having white/black lists for connecting to a virtual host would be useful. > Questions: > - need to provide an easy way for operate to maintain, secure & backup this > list > - should consider what to do if there file/props etc for this are > corrupt/format wrong > - if possible, the security filtering this provides should be part of a > potential chain of access REDUCING plugins so that this is easy to drop in > and teams can potentially write their own reducing filter class and use > abstraction to define in config for broker > - needs to be at vhost level, and potentially at queue level ? > > Explicit allow/deny lists of connection patterns on virtualhosts in > config.xml, existing ACL infrastructure for entities below that. > Pattern would be one of: > IP address > CIDR mask > regexp on hostname > Changes would not be possible while broker was running, the file would need > to be editted and then the broker restarted. This avoids the necessity to > consider what happens to existing connections which would be excluded by a > new rule. Errors in configuration would prevent broker startup. > Implementation wise, a new IPRestriction class would extend ACLPlugin which > listens for ConnectionOpen and checks against the list of rules. > AMQProtocolSession needs to expose access to the underlying socket. > --- > We may need to reconsider allowing changes to the lists while the broker is > running. It would probably imply storing these outwith the main configuration > file and instead having something else, potentially a properties file, which > could be editted by the broker as it runs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
On Thu, Jan 22, 2009 at 3:00 PM, Carl Trieloff wrote: > Lahiru Gunathilake wrote: >> >> On Thu, Jan 22, 2009 at 6:57 AM, Marnie McCormack < >> marnie.mccorm...@googlemail.com> wrote: >> >> >>> >>> Apache Qpid, Enterprise Messaging through AMQP > > > Apache Qpid, AMQP Enterprise Messaging that just works. It's pretty similar to the title of RabbitMQ's tech talk: http://www.rabbitmq.com/resources/google-tech-talk-final/google.html - Aidan -- Apache Qpid - World Domination through Advanced Message Queueing http://qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
Lahiru Gunathilake wrote: On Thu, Jan 22, 2009 at 6:57 AM, Marnie McCormack < marnie.mccorm...@googlemail.com> wrote: Apache Qpid, Enterprise Messaging through AMQP Apache Qpid, AMQP Enterprise Messaging that just works. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1583) IP White/Black lists for virtual hosts
[ https://issues.apache.org/jira/browse/QPID-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666161#action_12666161 ] Aidan Skinner commented on QPID-1583: - The downside to adding this to the virtualhost file is that it wouldn't be dynamically reloaded, or modified with the management console. It would be possible to teach Qpid about kill -HUP to re-read it's config files, although this raises questions about what to do with things like the store directory if that changes. Other options include: seperate out the access file to something akin to postgresql's pg_hba.conf allow JMX to add or remove rules, but not persist these to disk all of the above I don't think rewriting the virtualhosts file is a great idea, it means the brokers config has to be writable by the user the broker is running as. > IP White/Black lists for virtual hosts > -- > > Key: QPID-1583 > URL: https://issues.apache.org/jira/browse/QPID-1583 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: M5 >Reporter: Aidan Skinner >Assignee: Aidan Skinner > Fix For: M5 > > > Having white/black lists for connecting to a virtual host would be useful. > Questions: > - need to provide an easy way for operate to maintain, secure & backup this > list > - should consider what to do if there file/props etc for this are > corrupt/format wrong > - if possible, the security filtering this provides should be part of a > potential chain of access REDUCING plugins so that this is easy to drop in > and teams can potentially write their own reducing filter class and use > abstraction to define in config for broker > - needs to be at vhost level, and potentially at queue level ? > > Explicit allow/deny lists of connection patterns on virtualhosts in > config.xml, existing ACL infrastructure for entities below that. > Pattern would be one of: > IP address > CIDR mask > regexp on hostname > Changes would not be possible while broker was running, the file would need > to be editted and then the broker restarted. This avoids the necessity to > consider what happens to existing connections which would be excluded by a > new rule. Errors in configuration would prevent broker startup. > Implementation wise, a new IPRestriction class would extend ACLPlugin which > listens for ConnectionOpen and checks against the list of rules. > AMQProtocolSession needs to expose access to the underlying socket. > --- > We may need to reconsider allowing changes to the lists while the broker is > running. It would probably imply storing these outwith the main configuration > file and instead having something else, potentially a properties file, which > could be editted by the broker as it runs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
On Thu, Jan 22, 2009 at 6:57 AM, Marnie McCormack < marnie.mccorm...@googlemail.com> wrote: > Apache Qpid, Enterprise Messaging through AMQP Short and sweet for me.. :-) +1 > > > On Thu, Jan 22, 2009 at 2:24 PM, Aidan Skinner >wrote: > > > On Thu, Jan 22, 2009 at 2:01 PM, Carl Trieloff > > wrote: > > > > > Mark Atwell wrote: > > >> > > >> Generally, one wants to avoid (even implied) SLAs or other formal > > >> measurable > > >> 'commitments' in logos & slogans. > > > > +1 > > > > > For our users list > > > > > > Apache Qpid, AMQP that just works. > > > > I'd probably go for one slogan for all lists. I also think that we > > should be explicit about being a messaging solution, not everybody > > will know what Qpid or AMQP actually are. I > > > > I've been using the thing in my .sig for a while now, but it's > > probably not quite right for the project as a whole. > > > > - Aidan > > -- > > Apache Qpid - World Domination through Advanced Message Queueing > > http://qpid.apache.org > > > > - > > Apache Qpid - AMQP Messaging Implementation > > Project: http://qpid.apache.org > > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > > > > -- Apache Qpid, Worlds dominant messaging middleware..!!!
Re: Qpid slogan?
Apache Qpid, Enterprise Messaging through AMQP On Thu, Jan 22, 2009 at 2:24 PM, Aidan Skinner wrote: > On Thu, Jan 22, 2009 at 2:01 PM, Carl Trieloff > wrote: > > > Mark Atwell wrote: > >> > >> Generally, one wants to avoid (even implied) SLAs or other formal > >> measurable > >> 'commitments' in logos & slogans. > > +1 > > > For our users list > > > > Apache Qpid, AMQP that just works. > > I'd probably go for one slogan for all lists. I also think that we > should be explicit about being a messaging solution, not everybody > will know what Qpid or AMQP actually are. I > > I've been using the thing in my .sig for a while now, but it's > probably not quite right for the project as a whole. > > - Aidan > -- > Apache Qpid - World Domination through Advanced Message Queueing > http://qpid.apache.org > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > >
Re: Qpid slogan?
On Thu, Jan 22, 2009 at 2:01 PM, Carl Trieloff wrote: > Mark Atwell wrote: >> >> Generally, one wants to avoid (even implied) SLAs or other formal >> measurable >> 'commitments' in logos & slogans. +1 > For our users list > > Apache Qpid, AMQP that just works. I'd probably go for one slogan for all lists. I also think that we should be explicit about being a messaging solution, not everybody will know what Qpid or AMQP actually are. I I've been using the thing in my .sig for a while now, but it's probably not quite right for the project as a whole. - Aidan -- Apache Qpid - World Domination through Advanced Message Queueing http://qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid slogan?
Mark Atwell wrote: Generally, one wants to avoid (even implied) SLAs or other formal measurable 'commitments' in logos & slogans. A couple of thoughts: - Apache Qpid: *The* AMQP Implementation - Apache Qpid: Advanced Messaging, Quick, Purposeful I'm sure that there may be some better variants to Quick & Purposeful! M For our users list Apache Qpid, AMQP that just works. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1418) TimeToLiveTest.testPassiveTTL failed
[ https://issues.apache.org/jira/browse/QPID-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner updated QPID-1418: Status: Ready To Review (was: In Progress) > TimeToLiveTest.testPassiveTTL failed > - > > Key: QPID-1418 > URL: https://issues.apache.org/jira/browse/QPID-1418 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Reporter: Martin Ritchie >Assignee: Martin Ritchie >Priority: Minor > Attachments: TEST-org.apache.qpid.server.queue.TimeToLiveTest.txt > > > testPassiveTTL > org.apache.qpid.server.queue.TimeToLiveTest > junit.framework.AssertionFailedError: Final message has incorrect TTL. > expected:<0> but was:<1000> > at > org.apache.qpid.server.queue.TimeToLiveTest.testPassiveTTL(TimeToLiveTest.java:158) > Will attach log. > This would suggest that the passive ttl message did not timeout. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1418) TimeToLiveTest.testPassiveTTL failed
[ https://issues.apache.org/jira/browse/QPID-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666132#action_12666132 ] Aidan Skinner commented on QPID-1418: - I think 736618 should fix this > TimeToLiveTest.testPassiveTTL failed > - > > Key: QPID-1418 > URL: https://issues.apache.org/jira/browse/QPID-1418 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Reporter: Martin Ritchie >Assignee: Martin Ritchie >Priority: Minor > Attachments: TEST-org.apache.qpid.server.queue.TimeToLiveTest.txt > > > testPassiveTTL > org.apache.qpid.server.queue.TimeToLiveTest > junit.framework.AssertionFailedError: Final message has incorrect TTL. > expected:<0> but was:<1000> > at > org.apache.qpid.server.queue.TimeToLiveTest.testPassiveTTL(TimeToLiveTest.java:158) > Will attach log. > This would suggest that the passive ttl message did not timeout. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1610) Can't allow both temporary and durable topic subscriptions for the same user with ACLs
[ https://issues.apache.org/jira/browse/QPID-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666127#action_12666127 ] Aidan Skinner commented on QPID-1610: - It's worth noting there's a workaround for this, just use different users for temporary and durable topic subscriptions. > Can't allow both temporary and durable topic subscriptions for the same user > with ACLs > -- > > Key: QPID-1610 > URL: https://issues.apache.org/jira/browse/QPID-1610 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: M4, M5 >Reporter: Aidan Skinner > > PrincipalPermissions.authorise does not allow temporary queues and named > queues to be created by the same user due to the check currently only line > 471: > // If there is a white list then check > return create_queues_queues == null || > create_queues_queues.containsKey(queueName); > create_queues_queueus will never be null, it should check size() == 0 like > the equivalent test in the CONSUME case does. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-1610) Can't allow both temporary and durable topic subscriptions for the same user with ACLs
Can't allow both temporary and durable topic subscriptions for the same user with ACLs -- Key: QPID-1610 URL: https://issues.apache.org/jira/browse/QPID-1610 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: M4, M5 Reporter: Aidan Skinner PrincipalPermissions.authorise does not allow temporary queues and named queues to be created by the same user due to the check currently only line 471: // If there is a white list then check return create_queues_queues == null || create_queues_queues.containsKey(queueName); create_queues_queueus will never be null, it should check size() == 0 like the equivalent test in the CONSUME case does. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-1418) TimeToLiveTest.testPassiveTTL failed
[ https://issues.apache.org/jira/browse/QPID-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie reassigned QPID-1418: Assignee: Martin Ritchie > TimeToLiveTest.testPassiveTTL failed > - > > Key: QPID-1418 > URL: https://issues.apache.org/jira/browse/QPID-1418 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Reporter: Martin Ritchie >Assignee: Martin Ritchie >Priority: Minor > Attachments: TEST-org.apache.qpid.server.queue.TimeToLiveTest.txt > > > testPassiveTTL > org.apache.qpid.server.queue.TimeToLiveTest > junit.framework.AssertionFailedError: Final message has incorrect TTL. > expected:<0> but was:<1000> > at > org.apache.qpid.server.queue.TimeToLiveTest.testPassiveTTL(TimeToLiveTest.java:158) > Will attach log. > This would suggest that the passive ttl message did not timeout. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Git workflow for non-comitters
I'm totally in love with git, and I think you should be too. I think it's particularly useful for non-comitters, since it allows local commits and branches which should make tracking trunk easier. git format-patch makes getting your changes into a jira-able format a doodle. Here's how I'd use git to do this: git clone git://jukka.zitting.name/qpid.git qpid [1] git checkout -b QPID-2342 [I name branches for the jira, easier to remember what goes with what] [... hack hack hack ...] git commit [... time passes ...] git checkout master git pull origin git checkout QPID-2342 git rebase master [... fix up conflicts, make further changes etc ...] git commit git rebase -i HEAD~2 [lets you merge fix ups back into the main revision again, totally sweet] mkdir -p ~/src/patches/QPID-2342/ git format-patch master -o ~/src/patches/QPID-2342/ then attach the patches to the Jira using your favourite webbrowser. - Aidan [1] Also available at http://jukka.zitting.name/git/r/qpid.git if git:// doesn't work for you -- Apache Qpid - World Domination through Advanced Message Queueing http://qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: [Vote] Release RC9 as M4
Awwh, shucks. Thanks Rafi - and well done for getting M4 out the door ! Made me smile. I shall endeavour to kep it up for M5 :-) Regards, Marnie On Tue, Jan 20, 2009 at 5:59 PM, Rafael Schloming wrote: > Gordon Sim wrote: > >> Rafael Schloming wrote: >> >>> Rafael Schloming wrote: >>> Here's the eagerly awaited M4 RC9: http://people.apache.org/~rhs/qpid-M4-RC9/ Please review and vote. >>> >>> By my count we have 7 +1's and no 0 or -1's, so I'm going to close the >>> vote and declare RC9 is officially M4. I've copied it into the qpid dist >>> directory, so hopefully it should show up at www.apache.org/dist/qpid/M4on >>> the next sync. >>> >> >> Rafi, thank you very much for all your hard work on getting this through >> to release! Thanks also to all who took time to try it out (and of course to >> all those who fixed the issues found). >> > > You're quite welcome. > > I'd like to add my thanks to all those who helped out, and in particular to > Marnie whose heroic job of cleaning up JIRA was essential to the release. > > --Rafael > > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > >
Re: svn commit: r736349 - in /qpid/trunk/qpid/java/management/eclipse-plugin: ./ bin/ src/main/resources/ src/main/resources/linux-gtk-x86/ src/main/resources/linux-gtk-x86/Configuration/ src/main/r
Appologies Robbie, I didn't realise I was in the management directory when I did the commit. So used to git committing all changes forgot to check where I was for the svn commit. All the library updates and build.deps changes should be there now. Cheers Martin 2009/1/21 Robbie Gemmell : > The qpid/java/build.deps file should also have been updated but wasn't > > > -Original Message- > From: ritch...@apache.org [mailto:ritch...@apache.org] > Sent: 21 January 2009 17:42 > To: comm...@qpid.apache.org > Subject: svn commit: r736349 - in > /qpid/trunk/qpid/java/management/eclipse-plugin: ./ bin/ src/main/resources/ > src/main/resources/linux-gtk-x86/ > src/main/resources/linux-gtk-x86/Configuration/ > src/main/resources/macosx/Configuration/ src/main/resources/macosx/C... > > Author: ritchiem > Date: Wed Jan 21 09:41:46 2009 > New Revision: 736349 > > URL: http://svn.apache.org/viewvc?rev=736349&view=rev > Log: > QPID-1592 : Patch provided by Robert Gemmell to standardise launchers for > management console. > > Added: > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/linux-gtk-x86/libcairo-swt.so >(with props) > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/linux-gtk-x86/qpidmc >(with props) > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/macosx/Contents/MacOS/qpidmc >(props changed) > - copied unchanged from r736327, > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/macosx/Contents/MacOS/eclipse > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/win32-win32-x86/qpidmc.exe >(with props) > Removed: >qpid/trunk/qpid/java/management/eclipse-plugin/bin/ > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/license.eclipse.txt > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/linux-gtk-x86/eclipse.ini > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/macosx/Contents/MacOS/eclipse > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/macosx/Contents/MacOS/eclipse.ini > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/startup.jar >qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/unix/ >qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/win32/ > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/win32-win32-x86/eclipse.exe > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/win32-win32-x86/eclipse.ini > Modified: > > qpid/trunk/qpid/java/management/eclipse-plugin/build-release-common.properties > > qpid/trunk/qpid/java/management/eclipse-plugin/build-release-linux-gtk-x86.properties > > qpid/trunk/qpid/java/management/eclipse-plugin/build-release-macosx.properties >qpid/trunk/qpid/java/management/eclipse-plugin/build-release-macosx.xml > > qpid/trunk/qpid/java/management/eclipse-plugin/build-release-win32-win32-x86.properties >qpid/trunk/qpid/java/management/eclipse-plugin/build-release.xml >qpid/trunk/qpid/java/management/eclipse-plugin/build.xml > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/linux-gtk-x86/Configuration/config.ini > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/linux-gtk-x86/qpidmc.ini > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/macosx/Configuration/config.ini > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/macosx/Contents/Info.plist > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/macosx/Contents/MacOS/qpidmc.ini > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/qpid-management-common-plugin/MANIFEST.MF > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/win32-win32-x86/Configuration/config.ini > > qpid/trunk/qpid/java/management/eclipse-plugin/src/main/resources/win32-win32-x86/qpidmc.ini > > Modified: > qpid/trunk/qpid/java/management/eclipse-plugin/build-release-common.properties > URL: > http://svn.apache.org/viewvc/qpid/trunk/qpid/java/management/eclipse-plugin/build-release-common.properties?rev=736349&r1=736348&r2=736349&view=diff > == > > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > -- Martin Ritchie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1168) ACL and RBAC
[ https://issues.apache.org/jira/browse/QPID-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666091#action_12666091 ] Martin Ritchie commented on QPID-1168: -- The overall ACL design documentation can be found here: http://cwiki.apache.org/confluence/display/qpid/Qpid+ACL As a project we haven't yet addressed RBAC as far as I understand it. The ACL design only extends to users that can be members of groups. I've added the design details for the implementation work I have done on implementing the ACLv2 specification on this wiki page: http://cwiki.apache.org/confluence/display/qpid/FileACL+Design > ACL and RBAC > > > Key: QPID-1168 > URL: https://issues.apache.org/jira/browse/QPID-1168 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Reporter: Martin Ritchie >Assignee: Martin Ritchie > Fix For: M5 > > > Cloned from QPID-107 to capture the work done on the Java Broker > Implement ACL and RBAC for both brokers (Java) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
