[jira] [Commented] (QPID-658) NoLocal messages should be deleted when the queue is exclusive
[ https://issues.apache.org/jira/browse/QPID-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130919#comment-14130919 ] ASF subversion and git services commented on QPID-658: -- Commit 1624429 from cliffjan...@apache.org in branch 'proton/trunk' [ https://svn.apache.org/r1624429 ] QPID-658 Windows driver.c with selectors and selectables > NoLocal messages should be deleted when the queue is exclusive > -- > > Key: QPID-658 > URL: https://issues.apache.org/jira/browse/QPID-658 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, Java Client >Affects Versions: M3 >Reporter: Arnaud Simon >Assignee: Gordon Sim > Fix For: 0.6 > > > For JMS we need the broker to delete messages of an exclusive queue that > cannot be delivered to the consumer because of Nolocal. This is a simple fix > for supporting the JMS notion of noLocal (topic only). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Review Request 25100: Provide access to the Proton version numbers (major, minor) via the bindings (python only atm)
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25100/#review53083 --- I think this patch overlaps with what is already on trunk. If you notice PROTON-651 has a couple of commits on it already to do at least part of what is in this patch. - Rafael Schloming On Aug. 27, 2014, 3:31 p.m., Kenneth Giusti wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/25100/ > --- > > (Updated Aug. 27, 2014, 3:31 p.m.) > > > Review request for qpid, Justin Ross, Darryl Pierce, Rafael Schloming, and > Robbie Gemmell. > > > Bugs: proton-651 > https://issues.apache.org/jira/browse/proton-651 > > > Repository: qpid > > > Description > --- > > Simple export of the version #'s. I did have to add these to the Java side, > not sure how you feel about that. I'm not comfortable updating the other > bindings - don't think I can make the best choice as to what feels 'natural' > for the other bindings. > > > Diffs > - > > proton/trunk/proton-c/bindings/python/proton.py 1620643 > proton/trunk/proton-c/include/proton/cproton.i 1620643 > proton/trunk/proton-c/include/proton/version.h.in 1620643 > proton/trunk/proton-j/src/main/java/org/apache/qpid/proton/Proton.java > 1620643 > proton/trunk/proton-j/src/main/resources/cproton.py 1620643 > proton/trunk/proton-j/src/main/resources/cversion.py PRE-CREATION > > Diff: https://reviews.apache.org/r/25100/diff/ > > > Testing > --- > > existing unit tests pass. Verified that the proton.VERSION_MAJOR/MINOR > values are correct by hand. > > > Thanks, > > Kenneth Giusti > >
[jira] [Commented] (QPID-6093) UI to expose read/write operations for context name/value pairs
[ https://issues.apache.org/jira/browse/QPID-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130353#comment-14130353 ] ASF subversion and git services commented on QPID-6093: --- Commit 1624345 from oru...@apache.org in branch 'qpid/trunk' [ https://svn.apache.org/r1624345 ] QPID-6093: Add UI to set context variables > UI to expose read/write operations for context name/value pairs > --- > > Key: QPID-6093 > URL: https://issues.apache.org/jira/browse/QPID-6093 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy >Assignee: Alex Rudyy > Fix For: 0.31 > > > Add UI to edit and add context variables for the following COs: > Broker > Virtual Host Node > Virtual Host > The control to set context variables should be displayed in a Panel folded by > default. User would need to expand the panel in order to edit context > variables. > Both inherited and local context variables should be displayed with their > effective and actual values. > Local variables should be easily distinguished from inherited (highlighted > with bold font). > Only actual values should be editable. > User should be able to toggle between local context variables and inherited > context variables. > System should be designed in such a way that functionality can be plugged > into all COs. > Context variables editing UI should be added into create and edit dialogs. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-6093) UI to expose read/write operations for context name/value pairs
[ https://issues.apache.org/jira/browse/QPID-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-6093: Assignee: Alex Rudyy > UI to expose read/write operations for context name/value pairs > --- > > Key: QPID-6093 > URL: https://issues.apache.org/jira/browse/QPID-6093 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy >Assignee: Alex Rudyy > Fix For: 0.31 > > > Add UI to edit and add context variables for the following COs: > Broker > Virtual Host Node > Virtual Host > The control to set context variables should be displayed in a Panel folded by > default. User would need to expand the panel in order to edit context > variables. > Both inherited and local context variables should be displayed with their > effective and actual values. > Local variables should be easily distinguished from inherited (highlighted > with bold font). > Only actual values should be editable. > User should be able to toggle between local context variables and inherited > context variables. > System should be designed in such a way that functionality can be plugged > into all COs. > Context variables editing UI should be added into create and edit dialogs. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-6093) UI to expose read/write operations for context name/value pairs
Alex Rudyy created QPID-6093: Summary: UI to expose read/write operations for context name/value pairs Key: QPID-6093 URL: https://issues.apache.org/jira/browse/QPID-6093 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Alex Rudyy Fix For: 0.31 Add UI to edit and add context variables for the following COs: Broker Virtual Host Node Virtual Host The control to set context variables should be displayed in a Panel folded by default. User would need to expand the panel in order to edit context variables. Both inherited and local context variables should be displayed with their effective and actual values. Local variables should be easily distinguished from inherited (highlighted with bold font). Only actual values should be editable. User should be able to toggle between local context variables and inherited context variables. System should be designed in such a way that functionality can be plugged into all COs. Context variables editing UI should be added into create and edit dialogs. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-6075) Deleting VHN fails to delete underlying store files if VHN has not been started
[ https://issues.apache.org/jira/browse/QPID-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-6075: Assignee: Andrew MacBean > Deleting VHN fails to delete underlying store files if VHN has not been > started > --- > > Key: QPID-6075 > URL: https://issues.apache.org/jira/browse/QPID-6075 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.30, 0.31 >Reporter: Keith Wall >Assignee: Andrew MacBean > > Deleting a VHN should delete any files owned by the underlying store. There > is a circumstance where this fails to happen. > # Create a Derby VHN with Provided VH > # Stop the VHN > # Restart the Broker > # Delete the VHN > # VHN removed successfully from the list of VHNs, however, it underlying > store files are still present on disk (DEFECT) > The issue is that ConfigurationStore implementations don't learn their > storeLocation until they are opened. If the store is not opened (as is the > case in the sequence above, or in the case of BDB HA, if a node never becomes > MASTER), the the ConfigurationStore has no knowledge of the store location > when #onDelete is called. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6092) Editing permitted node list to be allowed when VHN is master or in STOPPED/ERRORed state
[ https://issues.apache.org/jira/browse/QPID-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130085#comment-14130085 ] Andrew MacBean commented on QPID-6092: -- UI commit to follow > Editing permitted node list to be allowed when VHN is master or in > STOPPED/ERRORed state > > > Key: QPID-6092 > URL: https://issues.apache.org/jira/browse/QPID-6092 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > > The permitted node list should be editable only when the node is master, or > the node is in error/stopped state. > Validation to be enforced both client and server side. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6092) Editing permitted node list to be allowed when VHN is master or in STOPPED/ERRORed state
[ https://issues.apache.org/jira/browse/QPID-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130082#comment-14130082 ] ASF subversion and git services commented on QPID-6092: --- Commit 1624299 from [~macbean] in branch 'qpid/trunk' [ https://svn.apache.org/r1624299 ] QPID-6092: [Java Broker] Editing permitted node list to be allowed when VHN is master or in STOPPED/ERRORED state. Server (1/2) > Editing permitted node list to be allowed when VHN is master or in > STOPPED/ERRORed state > > > Key: QPID-6092 > URL: https://issues.apache.org/jira/browse/QPID-6092 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > > The permitted node list should be editable only when the node is master, or > the node is in error/stopped state. > Validation to be enforced both client and server side. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6090) Disallow a removal of permitted node entry from BDB HA VHN attribute "permittedNodes", if that node is already a member of a group
[ https://issues.apache.org/jira/browse/QPID-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130077#comment-14130077 ] Andrew MacBean commented on QPID-6090: -- Alex please review again thanks > Disallow a removal of permitted node entry from BDB HA VHN attribute > "permittedNodes", if that node is already a member of a group > -- > > Key: QPID-6090 > URL: https://issues.apache.org/jira/browse/QPID-6090 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Alex Rudyy > > New validation needs to be enforced so that on removal of node entry from > "permittedNodes", if removing node entry is already a member of the group, > the new "permittedNodes" nodes entry should not be stored in the > configuration store and an exception should be thrown. > We need to change UI to disallow a removal of permitted node entry from BDB > HA VH attribute "permittedNodes", if that node is already a member of a group -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6090) Disallow a removal of permitted node entry from BDB HA VHN attribute "permittedNodes", if that node is already a member of a group
[ https://issues.apache.org/jira/browse/QPID-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130075#comment-14130075 ] ASF subversion and git services commented on QPID-6090: --- Commit 1624298 from [~macbean] in branch 'qpid/trunk' [ https://svn.apache.org/r1624298 ] QPID-6090: [Java Broker] Change based on code review to protect against intruder case > Disallow a removal of permitted node entry from BDB HA VHN attribute > "permittedNodes", if that node is already a member of a group > -- > > Key: QPID-6090 > URL: https://issues.apache.org/jira/browse/QPID-6090 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Alex Rudyy > > New validation needs to be enforced so that on removal of node entry from > "permittedNodes", if removing node entry is already a member of the group, > the new "permittedNodes" nodes entry should not be stored in the > configuration store and an exception should be thrown. > We need to change UI to disallow a removal of permitted node entry from BDB > HA VH attribute "permittedNodes", if that node is already a member of a group -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6091) Qpid should configure SASL
[ https://issues.apache.org/jira/browse/QPID-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130012#comment-14130012 ] Brian Bouterse commented on QPID-6091: -- This could be treated as a docs bug, and the claim of configuring the SASL db with guest/guest be removed from the docs. That probably makes more sense then adding back the sasldb creation behavior because default usernames and passwords are insecure, but give the sense of security. Thanks Pavel for the workaround suggestions. > Qpid should configure SASL > -- > > Key: QPID-6091 > URL: https://issues.apache.org/jira/browse/QPID-6091 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.26 > Environment: RHEL6, RHEL7, Fedora 20 >Reporter: Brian Bouterse > > I expect Qpid to create a SASL database with a single user named 'guest' and > password 'guest' as part of the install of the C++ broker. > I expect this because the docs [0] say "The SASL database is installed at > /var/lib/qpidd/qpidd.sasldb; initially, it has one user named guest in the > QPID realm, and the password for this user is guest.". > The later version of Qpid docs also have similar statements, so I don't think > the claim was removed from a later Qpid verison. I also believe the later > versions (0.28+) don't install the SASL db either so it's broken in lots of > versions. > Both the Pulp and Kombu communities want a great out of the box use of Qpid. > The user should be able to install the right rpms, start the services, and it > just works. It would today, but the SASL db is not being created as the docs > indicate. > [0]: > http://qpid.apache.org/releases/qpid-0.26/cpp-broker/book/chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-User_Authentication-Configuring_SASL -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5861) Refactor Port implementations to remove the need for availableProtocols attribute
[ https://issues.apache.org/jira/browse/QPID-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey closed QPID-5861. - Resolution: Fixed This issue was resolved by the work on QPID-6010 > Refactor Port implementations to remove the need for availableProtocols > attribute > - > > Key: QPID-5861 > URL: https://issues.apache.org/jira/browse/QPID-5861 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall > > Remove use of the Port attribute availableProtocols and replace with > protocols. Refactor the protocols attribute to use the CO's model defaulting > mechanism to assign the correct protocol defaults based on each port type. > The AMQP port type needs to respect the protocol inclusions/exclusions system > properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5934) [Java Broker] Allow TTL to be overridden on a per-Queue basis
[ https://issues.apache.org/jira/browse/QPID-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-5934. --- Resolution: Fixed > [Java Broker] Allow TTL to be overridden on a per-Queue basis > - > > Key: QPID-5934 > URL: https://issues.apache.org/jira/browse/QPID-5934 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.29 > > > Rather than relying on the sender to correctly set TTL, it is sometimes > useful to be able to override the TTL on messages on a given queue (either to > ensure that messages on a given queue are expunged after a certain period of > time, or, conversely, to ensure that they are not expunged prematurely). > By setting a minimum and maximum message ttl time on a queue, the > administrator of the queue should be able to control what ttl values are > applied. (Note that if the message arrives in multiple queues, the ttl on one > queue should not affect the ttl on a separate queue). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6061) [Java Broker] [AMQP 1.0] The Java Broker does not properly implement the legacy filters as it never routes on subject
[ https://issues.apache.org/jira/browse/QPID-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-6061. --- Resolution: Fixed Fix Version/s: 0.31 > [Java Broker] [AMQP 1.0] The Java Broker does not properly implement the > legacy filters as it never routes on subject > - > > Key: QPID-6061 > URL: https://issues.apache.org/jira/browse/QPID-6061 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.31 > > > The "legacy filters" defined for AMQP 1.0 are phrased in terms of routing > based on subject, however the Java Broker never routes at an exchange based > on subject. > In the case where a message is sent to the destination foo and foo is an > exchange of type "direct", or "topic" then the message subject should be used > as the routing key if the subject is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6047) [Java Broker] When converting an AMQP 1.0 message into an AMQP 0-10 message place the subject into the application property qpid.subject
[ https://issues.apache.org/jira/browse/QPID-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-6047. --- Resolution: Fixed Fix Version/s: 0.31 > [Java Broker] When converting an AMQP 1.0 message into an AMQP 0-10 message > place the subject into the application property qpid.subject > > > Key: QPID-6047 > URL: https://issues.apache.org/jira/browse/QPID-6047 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.31 > > > The application property "qpid.subject" is used by convention in 0-10 > messages to provide subject information. The message conversion between AMQP > 1.0 and AMQP 0-10 should take this into account. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6040) [Java Broker] Add the ability to create a single consumer that consumes from multiple queues
[ https://issues.apache.org/jira/browse/QPID-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-6040. --- Resolution: Fixed Fix Version/s: 0.31 > [Java Broker] Add the ability to create a single consumer that consumes from > multiple queues > > > Key: QPID-6040 > URL: https://issues.apache.org/jira/browse/QPID-6040 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.31 > > > For AMQP 0-10 in particular it is difficult to manage credit across multiple > consumers on a single session. If the aim of the user is simply to receive > messages from any one of a given set of queues, they may wish to limit the > total credit given to the queues (to reduce prefetch) without having to > specifically assign the credit to a particular queue of queues. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5965) [Java Broker] Store transient messages to disk (and remove from memory) when in low memory conditions
[ https://issues.apache.org/jira/browse/QPID-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-5965. --- Resolution: Fixed > [Java Broker] Store transient messages to disk (and remove from memory) when > in low memory conditions > - > > Key: QPID-5965 > URL: https://issues.apache.org/jira/browse/QPID-5965 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.29 > > > Currently the Java Broker will evacuate persistent messages from memory in > low memory situations, but does not do the same with transient messages. By > monitoring total queue size, we can determine when it may be appropriate to > force transient messages to disk (and thus make them eligible for evacuation > from memory) and in this way make the broker capable of withstanding periods > of increased retention of transient messages. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-6092) Editing permitted node list to be allowed when VHN is master or in STOPPED/ERRORed state
Andrew MacBean created QPID-6092: Summary: Editing permitted node list to be allowed when VHN is master or in STOPPED/ERRORed state Key: QPID-6092 URL: https://issues.apache.org/jira/browse/QPID-6092 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Andrew MacBean Assignee: Andrew MacBean The permitted node list should be editable only when the node is master, or the node is in error/stopped state. Validation to be enforced both client and server side. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6090) Disallow a removal of permitted node entry from BDB HA VHN attribute "permittedNodes", if that node is already a member of a group
[ https://issues.apache.org/jira/browse/QPID-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129818#comment-14129818 ] Andrew MacBean commented on QPID-6090: -- Alex, good question and valid point. I will make changes to the if guards to ensure that the node is part of the current set permitted nodes too so that it works around this scenario. Thanks, Andrew > Disallow a removal of permitted node entry from BDB HA VHN attribute > "permittedNodes", if that node is already a member of a group > -- > > Key: QPID-6090 > URL: https://issues.apache.org/jira/browse/QPID-6090 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Alex Rudyy > > New validation needs to be enforced so that on removal of node entry from > "permittedNodes", if removing node entry is already a member of the group, > the new "permittedNodes" nodes entry should not be stored in the > configuration store and an exception should be thrown. > We need to change UI to disallow a removal of permitted node entry from BDB > HA VH attribute "permittedNodes", if that node is already a member of a group -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6090) Disallow a removal of permitted node entry from BDB HA VHN attribute "permittedNodes", if that node is already a member of a group
[ https://issues.apache.org/jira/browse/QPID-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129771#comment-14129771 ] Alex Rudyy commented on QPID-6090: -- Andrew, I've got a question about implemented changes. It looks like when intruder node is connected and cluster is brought up in management mode, editing of permmittedNodes would require adding of intruder node into a list as methodgetRemoteReplicationNodes() would return a collection with an intruder node. Is it intentional? > Disallow a removal of permitted node entry from BDB HA VHN attribute > "permittedNodes", if that node is already a member of a group > -- > > Key: QPID-6090 > URL: https://issues.apache.org/jira/browse/QPID-6090 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Alex Rudyy > > New validation needs to be enforced so that on removal of node entry from > "permittedNodes", if removing node entry is already a member of the group, > the new "permittedNodes" nodes entry should not be stored in the > configuration store and an exception should be thrown. > We need to change UI to disallow a removal of permitted node entry from BDB > HA VH attribute "permittedNodes", if that node is already a member of a group -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6074) BDB HA VHN to use context variables rather than system property to control timeouts etc
[ https://issues.apache.org/jira/browse/QPID-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-6074. -- Resolution: Fixed The changes looks good to me. The declaration of context variables and their defaults on ReplicationEnvironmentFacade works for me. I do not have really objects about that. I just wanted to clarify whether that was intentional and there were no plan to change in order to make the code consistent with other context variable declarations > BDB HA VHN to use context variables rather than system property to control > timeouts etc > --- > > Key: QPID-6074 > URL: https://issues.apache.org/jira/browse/QPID-6074 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Alex Rudyy > Fix For: 0.31 > > > The BDB HA VHN implementation currently uses system properties for a number > of timeout values, polling frequencies and retry intervals. These should be > converted to context variables. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6091) Qpid should configure SASL
[ https://issues.apache.org/jira/browse/QPID-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129749#comment-14129749 ] Pavel Moravec commented on QPID-6091: - FYI one can use ANONYMOUS mechanism that does not require credentials (one can provide creds but they are ignored). Note that sasldb file is machine-independent. I.e. one can create the sasldb file just once (at least on one distro, not sure if Fedora/RHEL6/RHEL7 matters) and then copy to any node with qpid installed. > Qpid should configure SASL > -- > > Key: QPID-6091 > URL: https://issues.apache.org/jira/browse/QPID-6091 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.26 > Environment: RHEL6, RHEL7, Fedora 20 >Reporter: Brian Bouterse > > I expect Qpid to create a SASL database with a single user named 'guest' and > password 'guest' as part of the install of the C++ broker. > I expect this because the docs [0] say "The SASL database is installed at > /var/lib/qpidd/qpidd.sasldb; initially, it has one user named guest in the > QPID realm, and the password for this user is guest.". > The later version of Qpid docs also have similar statements, so I don't think > the claim was removed from a later Qpid verison. I also believe the later > versions (0.28+) don't install the SASL db either so it's broken in lots of > versions. > Both the Pulp and Kombu communities want a great out of the box use of Qpid. > The user should be able to install the right rpms, start the services, and it > just works. It would today, but the SASL db is not being created as the docs > indicate. > [0]: > http://qpid.apache.org/releases/qpid-0.26/cpp-broker/book/chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-User_Authentication-Configuring_SASL -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
