Re: 0.22 release update - proposed final RC4

Please go ahead. If we end up being ready, I'll produce the new RC later today. Justin On Sun, May 19, 2013 at 9:10 PM, Robbie Gemmell wrote: > In case it isn't clear that was me effectively asking permission, as I'd > rather not merge code changes to the branch unless they are going to be > in

[jira] [Updated] (QPID-4777) [Java Broker] Add UI to view and edit web management configuration

[ https://issues.apache.org/jira/browse/QPID-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4777: - Fix Version/s: 0.22 > [Java Broker] Add UI to view and edit web management configuration > ---

[jira] [Created] (QPID-4868) [Java Broker] Add UI into web management console to edit JMX management configuration

Alex Rudyy created QPID-4868: Summary: [Java Broker] Add UI into web management console to edit JMX management configuration Key: QPID-4868 URL: https://issues.apache.org/jira/browse/QPID-4868 Project: Qp

[jira] [Commented] (QPID-4868) [Java Broker] Add UI into web management console to edit JMX management configuration

[ https://issues.apache.org/jira/browse/QPID-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661910#comment-13661910 ] Alex Rudyy commented on QPID-4868: -- The fix is committed into trunk under revision http://

[jira] [Commented] (QPID-4854) max-negotiate-time feature breaks AMQP 1.0

[ https://issues.apache.org/jira/browse/QPID-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661923#comment-13661923 ] Gordon Sim commented on QPID-4854: -- An alternative might be to add an isHandshakeComplete(

[jira] [Resolved] (QPID-4851) [JMS AMQP 1.0] ConcurrentModificationException is thrown on closing of AMQP 1.0 connection with existing sessions

[ https://issues.apache.org/jira/browse/QPID-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4851. -- Resolution: Fixed Fix Version/s: 0.22 Rob mentioned to me he thought the change looked go

[jira] [Commented] (QPID-4851) [JMS AMQP 1.0] ConcurrentModificationException is thrown on closing of AMQP 1.0 connection with existing sessions

[ https://issues.apache.org/jira/browse/QPID-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661932#comment-13661932 ] Robbie Gemmell commented on QPID-4851: -- r1483121 merged to the 0.22 release branch via

[jira] [Updated] (QPID-4851) [JMS AMQP 1.0] ConcurrentModificationException is thrown on closing of AMQP 1.0 connection with existing sessions

[ https://issues.apache.org/jira/browse/QPID-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4851: - Affects Version/s: (was: 0.23) > [JMS AMQP 1.0] ConcurrentModificationException is thrown

[jira] [Commented] (QPID-4852) [Java Broker] Opened AMQP 1.0 connections are not get closed on broker shutdown

[ https://issues.apache.org/jira/browse/QPID-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661936#comment-13661936 ] Robbie Gemmell commented on QPID-4852: -- Rob mentioned to me he thought the change look

[jira] [Commented] (QPID-4852) [Java Broker] Opened AMQP 1.0 connections are not get closed on broker shutdown

[ https://issues.apache.org/jira/browse/QPID-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661939#comment-13661939 ] Robbie Gemmell commented on QPID-4852: -- r1483260 merged to the 0.22 release branch via

[jira] [Updated] (QPID-4852) [Java Broker] Opened AMQP 1.0 connections are not get closed on broker shutdown

[ https://issues.apache.org/jira/browse/QPID-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4852: - Affects Version/s: (was: 0.23) > [Java Broker] Opened AMQP 1.0 connections are not get clo

[jira] [Resolved] (QPID-4852) [Java Broker] Opened AMQP 1.0 connections are not get closed on broker shutdown

[ https://issues.apache.org/jira/browse/QPID-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4852. -- Resolution: Fixed Fix Version/s: 0.22 > [Java Broker] Opened AMQP 1.0 connections are

[jira] [Commented] (QPID-4863) [Java Broker] Validate plugin attribute changes and throw UnsupportedOperationException where attribute changes are not supported

[ https://issues.apache.org/jira/browse/QPID-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661943#comment-13661943 ] Robbie Gemmell commented on QPID-4863: -- r1483861 merged to the 0.22 release branch via

[jira] [Resolved] (QPID-4863) [Java Broker] Validate plugin attribute changes and throw UnsupportedOperationException where attribute changes are not supported

[ https://issues.apache.org/jira/browse/QPID-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4863. -- Resolution: Fixed Fix Version/s: (was: 0.23) 0.22 > [Java Brok

[jira] [Commented] (QPID-4739) [Java Broker] complete functionality to configure multiple key store and trust stores and assign them per-port

[ https://issues.apache.org/jira/browse/QPID-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661944#comment-13661944 ] Robbie Gemmell commented on QPID-4739: -- Alex made an additional change via http://svn.

[jira] [Commented] (QPID-4862) [Java Broker] Improve registration/unregistration for JMX MBean objects

[ https://issues.apache.org/jira/browse/QPID-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661945#comment-13661945 ] Robbie Gemmell commented on QPID-4862: -- r1483863 merged to the 0.22 release branch via

[jira] [Resolved] (QPID-4862) [Java Broker] Improve registration/unregistration for JMX MBean objects

[ https://issues.apache.org/jira/browse/QPID-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4862. -- Resolution: Fixed > [Java Broker] Improve registration/unregistration for JMX MBean objects

[jira] [Updated] (QPID-4862) [Java Broker] Improve registration/unregistration for JMX MBean objects

[ https://issues.apache.org/jira/browse/QPID-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4862: - Fix Version/s: (was: 0.23) 0.22 > [Java Broker] Improve registration/un

[jira] [Commented] (QPID-4851) [JMS AMQP 1.0] ConcurrentModificationException is thrown on closing of AMQP 1.0 connection with existing sessions

[ https://issues.apache.org/jira/browse/QPID-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661948#comment-13661948 ] Robbie Gemmell commented on QPID-4851: -- The log messages for commits r1483864 and r148

[jira] [Commented] (QPID-4861) [Java Broker] Allow users to access http management using '/' instead of forcing them to type '/management' or '/index.html'

[ https://issues.apache.org/jira/browse/QPID-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661949#comment-13661949 ] Robbie Gemmell commented on QPID-4861: -- r1483864 merged to the 0.22 release branch via

[jira] [Resolved] (QPID-4861) [Java Broker] Allow users to access http management using '/' instead of forcing them to type '/management' or '/index.html'

[ https://issues.apache.org/jira/browse/QPID-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4861. -- Resolution: Fixed Fix Version/s: (was: 0.23) 0.22 > [Java Brok

[jira] [Commented] (QPID-4860) [Java Broker] Transition virtual host into ERRORED state on failure to activate

[ https://issues.apache.org/jira/browse/QPID-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661950#comment-13661950 ] Robbie Gemmell commented on QPID-4860: -- r1483865 merged to the 0.22 release branch via

[jira] [Commented] (QPID-4868) [Java Broker] Add UI into web management console to edit JMX management configuration

[ https://issues.apache.org/jira/browse/QPID-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661952#comment-13661952 ] Robbie Gemmell commented on QPID-4868: -- r1484430 merged to the 0.22 release branch via

[jira] [Resolved] (QPID-4860) [Java Broker] Transition virtual host into ERRORED state on failure to activate

[ https://issues.apache.org/jira/browse/QPID-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4860. -- Resolution: Fixed Fix Version/s: (was: 0.23) 0.22 > [Java Brok

[jira] [Resolved] (QPID-4868) [Java Broker] Add UI into web management console to edit JMX management configuration

[ https://issues.apache.org/jira/browse/QPID-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4868. -- Resolution: Fixed > [Java Broker] Add UI into web management console to edit JMX management

[jira] [Commented] (QPID-4861) [Java Broker] Allow users to access http management using '/' instead of forcing them to type '/management' or '/index.html'

[ https://issues.apache.org/jira/browse/QPID-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661949#comment-13661949 ] Robbie Gemmell commented on QPID-4861: -- r1483864 merged to the 0.22 release branch via

[jira] [Commented] (QPID-4858) [Java Broker] HTTP management ports configured with 'HTTP' protocol and 'SSL' transport options will silently fail to use SSL

[ https://issues.apache.org/jira/browse/QPID-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661954#comment-13661954 ] Robbie Gemmell commented on QPID-4858: -- r1483866 merged to the 0.22 release branch via

[jira] [Commented] (QPID-4685) [Java Broker] update documentation to reflect changes to configuration etc

[ https://issues.apache.org/jira/browse/QPID-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661953#comment-13661953 ] Robbie Gemmell commented on QPID-4685: -- Additional changes made via http://svn.apache.

[jira] [Resolved] (QPID-4858) [Java Broker] HTTP management ports configured with 'HTTP' protocol and 'SSL' transport options will silently fail to use SSL

[ https://issues.apache.org/jira/browse/QPID-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4858. -- Resolution: Fixed > [Java Broker] HTTP management ports configured with 'HTTP' protocol and

Re: Remaining perl bindings issues in RC3

On Sun, May 19, 2013 at 06:41:57PM +0200, Jimmy Jones wrote: > RC4 looking much better, but QPID-4724 doesn't seem to have been included so > doesn't build until patch applied. If its too late, should it be added to the > release notes instead to manually apply? My bad. I've pulled this commit o

Re: 0.22 release update - proposed final RC4

Done. (As I'm sure is obvious from the JIRA and commit traffic, I also merged some other small bug fixes and improvements in keeping with the previous 'break it you fix it' discussion) Robbie On 20 May 2013 11:24, Justin Ross wrote: > Please go ahead. If we end up being ready, I'll produce th

Re: Custom ACL source

Are you using the Java or C++ broker? Robbie On 20 May 2013 13:42, Misha Nesterenko wrote: > Hello all > > I wonder is it possible to use custom acl source? There is a single > database for our users and I do not want security information to be > scattered among several sources, e.g. database a

Re: Custom ACL source

Hi sorry, I am using java broker On Mon, May 20, 2013 at 4:15 PM, Robbie Gemmell wrote: > Are you using the Java or C++ broker? > > Robbie > > On 20 May 2013 13:42, Misha Nesterenko wrote: > > > Hello all > > > > I wonder is it possible to use custom acl source? There is a single > > database

Re: how to install Cman packages in fedora 18 (Using "qpidc-0.20")

--Alan Conway Sorry for the delay. Your documentation gives very clear explanation. Thank you very much !! -- View this message in context: http://qpid.2158936.n2.nabble.com/how-to-install-Cman-packages-in-fedora-18-Using-qpidc-0-20-tp7588818p7593081.html Sent from the Apache Qpid developer

[jira] [Commented] (QPID-4865) HA Update documents for queue replication

[ https://issues.apache.org/jira/browse/QPID-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662010#comment-13662010 ] Justin Ross commented on QPID-4865: --- Approved for 0.22. > HA Update docu

[jira] [Commented] (QPID-4006) Introduce HA support for Java Broker

[ https://issues.apache.org/jira/browse/QPID-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662066#comment-13662066 ] Keith Wall commented on QPID-4006: -- Note that Alex's patch for handling of InsufficientAck

Re: Review Request: Address deadlock btw _messageDeliveryLock and _failoverMutex

> On May 13, 2013, 3:22 p.m., Robbie Gemmell wrote: > > http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/client/AMQConnection.java, > > line 873 > > > > > > Whitespace > > raj

[jira] [Created] (QPID-4869) Small fix: Perl shouldn't be required to build Qpid

Darryl L. Pierce created QPID-4869: -- Summary: Small fix: Perl shouldn't be required to build Qpid Key: QPID-4869 URL: https://issues.apache.org/jira/browse/QPID-4869 Project: Qpid Issue Type

Re: Custom ACL source

Then the answer is that it is theoretically possible for you to define your own ACL source, although it will involve a non-trivial amount of work for you to do so. The brokers authorisation functionality is provided via a pluggable interface and so it would 'only' be a case of case of you implement

Re: Review Request: Address deadlock btw _messageDeliveryLock and _failoverMutex

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/10738/#review20770 --- http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/mai

0.22 RFI: QPID-4869

QPID-4869: Small fix: Perl shouldn't be required to build Qpid In QPID-4724 a change included made building Perl required instead of option by failing the CMake generation phase if Perl was found but not the Perl development files. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Deliv

[jira] [Commented] (QPID-4869) Small fix: Perl shouldn't be required to build Qpid

[ https://issues.apache.org/jira/browse/QPID-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662094#comment-13662094 ] Darryl L. Pierce commented on QPID-4869: This is fixed on trunk. The commit is here

[jira] [Updated] (QPID-4869) Small fix: Perl shouldn't be required to build Qpid

[ https://issues.apache.org/jira/browse/QPID-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce updated QPID-4869: --- Affects Version/s: 0.22 > Small fix: Perl shouldn't be required to build Qpid > --

[jira] [Updated] (QPID-4869) Small fix: Perl shouldn't be required to build Qpid

[ https://issues.apache.org/jira/browse/QPID-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce updated QPID-4869: --- Fix Version/s: 0.23 > Small fix: Perl shouldn't be required to build Qpid > --

[jira] [Resolved] (QPID-4869) Small fix: Perl shouldn't be required to build Qpid

[ https://issues.apache.org/jira/browse/QPID-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce resolved QPID-4869. Resolution: Fixed > Small fix: Perl shouldn't be required to build Qpid > --

Re: Custom ACL source

That sounds great. If authorization may be implemented as a separate plugin that is great! Could you give me some directions for 0.22 and if that is no so burdensome also for 0.20 Thanks On Mon, May 20, 2013 at 7:23 PM, Robbie Gemmell wrote: > Then the answer is that it is theoretically possibl