[jira] [Commented] (QPID-6161) [Java Broker] Add support for virtual host aliasing
[ https://issues.apache.org/jira/browse/QPID-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178174#comment-14178174 ] ASF subversion and git services commented on QPID-6161: --- Commit 1633324 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1633324 ] QPID-6161 : use vhost names rather than vhost node names for the name aliases [Java Broker] Add support for virtual host aliasing --- Key: QPID-6161 URL: https://issues.apache.org/jira/browse/QPID-6161 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey Fix For: 0.31 Add the ability to configure how a connection request for a given host/virtualhost is translated to assigning to a virtual host inside the broker. Allow for multiple names to match the same virtualhost, for different ports to have different mappings, etc. -- 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-6168) On create or change, validate an object's attributes against its valid values
[ https://issues.apache.org/jira/browse/QPID-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178236#comment-14178236 ] ASF subversion and git services commented on QPID-6168: --- Commit 168 from [~k-wall] in branch 'qpid/trunk' [ https://svn.apache.org/r168 ] QPID-6168: [Java Broker] Valid values check not to be applied for non mandatory fields where no value passed On create or change, validate an object's attributes against its valid values - Key: QPID-6168 URL: https://issues.apache.org/jira/browse/QPID-6168 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Keith Wall Fix For: 0.31 In the Java Broker's model, attributes can be annotated with valid values. These are a set of possible values which it is legal for the attribute to be. This metadata is already exposed to clients (like the Web Mangement UI) in order to allow them to auto-populate drop downs (etc) with legal values without needless duplication of logic on the client side. Currently, the CO tier on the Broker side does not enforce that the attributes have a value from the valid value set. We have some per instance style validation that could be replaced with common code. -- 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-6168) On create or change, validate an object's attributes against its valid values
[ https://issues.apache.org/jira/browse/QPID-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-6168. -- Resolution: Fixed On create or change, validate an object's attributes against its valid values - Key: QPID-6168 URL: https://issues.apache.org/jira/browse/QPID-6168 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Keith Wall Fix For: 0.31 In the Java Broker's model, attributes can be annotated with valid values. These are a set of possible values which it is legal for the attribute to be. This metadata is already exposed to clients (like the Web Mangement UI) in order to allow them to auto-populate drop downs (etc) with legal values without needless duplication of logic on the client side. Currently, the CO tier on the Broker side does not enforce that the attributes have a value from the valid value set. We have some per instance style validation that could be replaced with common code. -- 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-6170) No support for AArch64 and PPC64LE architectures
Marcin Juszkiewicz created QPID-6170: Summary: No support for AArch64 and PPC64LE architectures Key: QPID-6170 URL: https://issues.apache.org/jira/browse/QPID-6170 Project: Qpid Issue Type: Bug Components: Build Tools Affects Versions: 0.30 Environment: Fedora 'rawhide' on AArch64 Reporter: Marcin Juszkiewicz qpid-cpp-0.30/src/qpid/legacystore/jrnl/jcfg.h header has set of checks to find out word size and endianness. But list of checks is quite short and buggy. It has arm64 added for iOS but lacks aarch64 checks (same architecture but GNU world is using original name of architecture). Also for PowerPC it is assumed that it is Big Endian while there are LE chips now as well. I have a patch which replaces all those checks with use of endian.h and bits/wordsize.h headers. It is not perfect solution as it assumes glibc but (IMHO) better than current situation is as it allows qpid to be built on any other Linux supported architecture -- 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] [Updated] (QPID-6170) No support for AArch64 and PPC64LE architectures
[ https://issues.apache.org/jira/browse/QPID-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcin Juszkiewicz updated QPID-6170: - Attachment: fix-endian-check.patch No support for AArch64 and PPC64LE architectures Key: QPID-6170 URL: https://issues.apache.org/jira/browse/QPID-6170 Project: Qpid Issue Type: Bug Components: Build Tools Affects Versions: 0.30 Environment: Fedora 'rawhide' on AArch64 Reporter: Marcin Juszkiewicz Attachments: fix-endian-check.patch qpid-cpp-0.30/src/qpid/legacystore/jrnl/jcfg.h header has set of checks to find out word size and endianness. But list of checks is quite short and buggy. It has arm64 added for iOS but lacks aarch64 checks (same architecture but GNU world is using original name of architecture). Also for PowerPC it is assumed that it is Big Endian while there are LE chips now as well. I have a patch which replaces all those checks with use of endian.h and bits/wordsize.h headers. It is not perfect solution as it assumes glibc but (IMHO) better than current situation is as it allows qpid to be built on any other Linux supported architecture -- 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-6171) [Java Common] Connection.getChannels() leaks a potentially thread-unsafe data structure
Rob Godfrey created QPID-6171: - Summary: [Java Common] Connection.getChannels() leaks a potentially thread-unsafe data structure Key: QPID-6171 URL: https://issues.apache.org/jira/browse/QPID-6171 Project: Qpid Issue Type: Bug Components: Java Common Reporter: Rob Godfrey Assignee: Rob Godfrey Fix For: 0.31 the collection returned by getChannels() may be modified by other threads, leading to unsafe iteration throwing ConcurrentModificationException. The returned object should instead be a copy of the data and the underlying map should use a thread safe implementation to allow for the safe copying of the values() collection while another thread may be modifying the map. -- 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-6171) [Java Common] Connection.getChannels() leaks a potentially thread-unsafe data structure
[ https://issues.apache.org/jira/browse/QPID-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178290#comment-14178290 ] ASF subversion and git services commented on QPID-6171: --- Commit 1633344 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1633344 ] QPID-6171 : make Connection.getChannels() return a data structure that can be safely iterated over [Java Common] Connection.getChannels() leaks a potentially thread-unsafe data structure --- Key: QPID-6171 URL: https://issues.apache.org/jira/browse/QPID-6171 Project: Qpid Issue Type: Bug Components: Java Common Reporter: Rob Godfrey Assignee: Rob Godfrey Fix For: 0.31 the collection returned by getChannels() may be modified by other threads, leading to unsafe iteration throwing ConcurrentModificationException. The returned object should instead be a copy of the data and the underlying map should use a thread safe implementation to allow for the safe copying of the values() collection while another thread may be modifying the map. -- 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-6172) [Java Broker] Ensure the type attribute is always in the actual attributes of a configured object
Rob Godfrey created QPID-6172: - Summary: [Java Broker] Ensure the type attribute is always in the actual attributes of a configured object Key: QPID-6172 URL: https://issues.apache.org/jira/browse/QPID-6172 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey Fix For: 0.31 For cases where an object is directly created, or where a type is calculated from other attributes, getType() will return the inferred type, but getAttribute(TYPE) will return null. As with ID we should always ensure the TYPE attribute appears in the map of actual attributes. -- 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-6172) [Java Broker] Ensure the type attribute is always in the actual attributes of a configured object
[ https://issues.apache.org/jira/browse/QPID-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178349#comment-14178349 ] ASF subversion and git services commented on QPID-6172: --- Commit 1633361 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1633361 ] QPID-6172 : Ensure the type attribute is always present in the actual attribute map [Java Broker] Ensure the type attribute is always in the actual attributes of a configured object - Key: QPID-6172 URL: https://issues.apache.org/jira/browse/QPID-6172 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey Fix For: 0.31 For cases where an object is directly created, or where a type is calculated from other attributes, getType() will return the inferred type, but getAttribute(TYPE) will return null. As with ID we should always ensure the TYPE attribute appears in the map of actual attributes. -- 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-6172) [Java Broker] Ensure the type attribute is always in the actual attributes of a configured object
[ https://issues.apache.org/jira/browse/QPID-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178386#comment-14178386 ] ASF subversion and git services commented on QPID-6172: --- Commit 1633375 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1633375 ] QPID-6172 : Fix test to account for the fact that TYPE is always present [Java Broker] Ensure the type attribute is always in the actual attributes of a configured object - Key: QPID-6172 URL: https://issues.apache.org/jira/browse/QPID-6172 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey Fix For: 0.31 For cases where an object is directly created, or where a type is calculated from other attributes, getType() will return the inferred type, but getAttribute(TYPE) will return null. As with ID we should always ensure the TYPE attribute appears in the map of actual attributes. -- 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-6173) Virtualhost corresponding to the replica should disallow attribute update
Keith Wall created QPID-6173: Summary: Virtualhost corresponding to the replica should disallow attribute update Key: QPID-6173 URL: https://issues.apache.org/jira/browse/QPID-6173 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Keith Wall For the HA case, we have a dummy virtual host object (BDBHAVH) used to represent the virtual host in the model when the mastership is elsewhere in the group. This object is already a no-op with respect to attempts to add or delete exchanges/queues, but currently silently ignores attribute updates. It would be preferable if the object positively rejected such updates. -- 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-6108) Java Broker - Document changes made by 0.30
[ https://issues.apache.org/jira/browse/QPID-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178568#comment-14178568 ] ASF subversion and git services commented on QPID-6108: --- Commit 1633406 from [~k-wall] in branch 'qpid/trunk' [ https://svn.apache.org/r1633406 ] QPID-6108: [Java Client 0.8 Docs] Bump recommended JDK to 1.7 Java Broker - Document changes made by 0.30 --- Key: QPID-6108 URL: https://issues.apache.org/jira/browse/QPID-6108 Project: Qpid Issue Type: Improvement Components: Documentation, Java Broker Reporter: Keith Wall Assignee: Keith Wall Attachments: 0001-QPID-6108-Java-Broker-Documentation-Updates-for-chan.patch * support for virtualhost.xml removed * introduction of VHN into the model * REST API changes * Queue messageDurability/TTL controls * Parallel recovery * Flow to disk * Multi node HA support -- 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-6154) Handle rollback of node when use of weak durability has allowed nodes to diverge
[ https://issues.apache.org/jira/browse/QPID-6154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178569#comment-14178569 ] ASF subversion and git services commented on QPID-6154: --- Commit 1633407 from [~k-wall] in branch 'qpid/trunk' [ https://svn.apache.org/r1633407 ] QPID-6154: [Java Broker] HA - Handle rollback of node when use of weak durability has allowed nodes to diverge Handle rollback of node when use of weak durability has allowed nodes to diverge Key: QPID-6154 URL: https://issues.apache.org/jira/browse/QPID-6154 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Keith Wall Labels: bdbstore, ha Attachments: 0001-QPID-6154-Java-Broker-Handle-rollback-of-node-when-u.patch JE throws an asynchronous exception (RolllbackException) to indicate that, owing to the use of weak durability options a node that is trying to rejoin the group has transactions that do not match those of the current master, and it must rollback one or more transactions in order to join. This condition can't occur in use of the group with default quorum options, but if a user were to use node priority zero, electable group override or designate primary (options that all weaken durability), creates the situation were nodes can diverge (split brain). In the case where JE detects this, it delivers a RollbackException asynchronously shortly after environment creation and requires that the environment restarts so the diverged transactions can be dropped. Java Broker should catch this exception, log it and organise for the environment to restart. -- 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-6173) Virtualhost corresponding to the replica should disallow attribute update
[ https://issues.apache.org/jira/browse/QPID-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178573#comment-14178573 ] ASF subversion and git services commented on QPID-6173: --- Commit 1633408 from [~k-wall] in branch 'qpid/trunk' [ https://svn.apache.org/r1633408 ] QPID-6173: [Java Broker] Disallow attribute updates to the BDBHAReplicaVirtualHost Virtualhost corresponding to the replica should disallow attribute update - Key: QPID-6173 URL: https://issues.apache.org/jira/browse/QPID-6173 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Keith Wall Labels: BDB, HA For the HA case, we have a dummy virtual host object (BDBHAVH) used to represent the virtual host in the model when the mastership is elsewhere in the group. This object is already a no-op with respect to attempts to add or delete exchanges/queues, but currently silently ignores attribute updates. It would be preferable if the object positively rejected such updates. -- 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-6171) [Java Common] Connection.getChannels() leaks a potentially thread-unsafe data structure
[ https://issues.apache.org/jira/browse/QPID-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-6171. -- Resolution: Fixed Changes look reasonable to me. [Java Common] Connection.getChannels() leaks a potentially thread-unsafe data structure --- Key: QPID-6171 URL: https://issues.apache.org/jira/browse/QPID-6171 Project: Qpid Issue Type: Bug Components: Java Common Reporter: Rob Godfrey Assignee: Rob Godfrey Fix For: 0.31 the collection returned by getChannels() may be modified by other threads, leading to unsafe iteration throwing ConcurrentModificationException. The returned object should instead be a copy of the data and the underlying map should use a thread safe implementation to allow for the safe copying of the values() collection while another thread may be modifying the map. -- 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-6174) [Java Broker] Expose mechanism for restricting the number of HTTP connections / queued requests
Rob Godfrey created QPID-6174: - Summary: [Java Broker] Expose mechanism for restricting the number of HTTP connections / queued requests Key: QPID-6174 URL: https://issues.apache.org/jira/browse/QPID-6174 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey Allow the setting of the min/max threads and the jobs queue size for the Jetty server which processes HTTP management requests -- 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-6174) [Java Broker] Expose mechanism for restricting the number of HTTP connections / queued requests
[ https://issues.apache.org/jira/browse/QPID-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178728#comment-14178728 ] ASF subversion and git services commented on QPID-6174: --- Commit 1633424 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1633424 ] QPID-6174 : Expose settings for restricting number of threads / queued jobs in HTTP management server [Java Broker] Expose mechanism for restricting the number of HTTP connections / queued requests --- Key: QPID-6174 URL: https://issues.apache.org/jira/browse/QPID-6174 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey Allow the setting of the min/max threads and the jobs queue size for the Jetty server which processes HTTP management requests -- 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-6175) [Java Broker] Allow restricting maximum size of a message to be accepted by the broker
Rob Godfrey created QPID-6175: - Summary: [Java Broker] Allow restricting maximum size of a message to be accepted by the broker Key: QPID-6175 URL: https://issues.apache.org/jira/browse/QPID-6175 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey As a protection against over large messages causing out of memory conditions (and because generally very large messages are a bad idea) add the ability to restrict the largest message size accepted. -- 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-6175) [Java Broker] Allow restricting maximum size of a message to be accepted by the broker
[ https://issues.apache.org/jira/browse/QPID-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179110#comment-14179110 ] ASF subversion and git services commented on QPID-6175: --- Commit 1633466 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1633466 ] QPID-6175 : [Java Broker] allow maximum message size to be restricted [Java Broker] Allow restricting maximum size of a message to be accepted by the broker -- Key: QPID-6175 URL: https://issues.apache.org/jira/browse/QPID-6175 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey As a protection against over large messages causing out of memory conditions (and because generally very large messages are a bad idea) add the ability to restrict the largest message size accepted. -- 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-6108) Java Broker - Document changes made by 0.30
[ https://issues.apache.org/jira/browse/QPID-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179127#comment-14179127 ] ASF subversion and git services commented on QPID-6108: --- Commit 1633469 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1633469 ] QPID-6108 : point to Java 7 SE (and not 6) java docs Java Broker - Document changes made by 0.30 --- Key: QPID-6108 URL: https://issues.apache.org/jira/browse/QPID-6108 Project: Qpid Issue Type: Improvement Components: Documentation, Java Broker Reporter: Keith Wall Assignee: Keith Wall Attachments: 0001-QPID-6108-Java-Broker-Documentation-Updates-for-chan.patch * support for virtualhost.xml removed * introduction of VHN into the model * REST API changes * Queue messageDurability/TTL controls * Parallel recovery * Flow to disk * Multi node HA support -- 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-6108) Java Broker - Document changes made by 0.30
[ https://issues.apache.org/jira/browse/QPID-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179135#comment-14179135 ] ASF subversion and git services commented on QPID-6108: --- Commit 1633470 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1633470 ] QPID-6108 : point to Java 7 SE (and not 6) java docs Java Broker - Document changes made by 0.30 --- Key: QPID-6108 URL: https://issues.apache.org/jira/browse/QPID-6108 Project: Qpid Issue Type: Improvement Components: Documentation, Java Broker Reporter: Keith Wall Assignee: Keith Wall Attachments: 0001-QPID-6108-Java-Broker-Documentation-Updates-for-chan.patch * support for virtualhost.xml removed * introduction of VHN into the model * REST API changes * Queue messageDurability/TTL controls * Parallel recovery * Flow to disk * Multi node HA support -- 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
