In ER6, the hornetq-server has one extra configurable property exposed. This is applicable to both runtime (deployment specific) and server subsystems. The property: "page-max-concurrent-io" => { "type" => INT, "description" => "The maximum number of concurrent reads allowed on paging", "expressions-allowed" => false, "nillable" => true, "default" => 5, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "all-services" },
Seems to be added in 8601dc25 on may 2nd
Server subsystem updated with the latest configuration for hornetq. Commit: http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=8601dc25257d4929c39e5c02c991cc40e70dac9f Deployment specific subsystem is not updated.
We need to determine how of much of this work, plus the remaining deployment specific work is exposed in the AS console. Depending on the answer to this will determine whether we clone bugs targeting for jon31 or jon32
This BZ only covers server subsystem updates. For deployment HornetQ updates please see bug 820757. Also, this BZ will cover any updates for existing sub-resources and the addition of missing sub-resources for the messaging subsystem or sub-resources.
master branch commits: http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commit;h=faa658c0f4d74dbc8e6bf18aae578797aca895d0 http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commit;h=7307c83165f5dc46445adc1b9f4dcee7877969af http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commit;h=1a24f57530a3df35b336fce7236b5fc1ecbd3429 http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commit;h=012356f528cefa0dbaead9f2113f610938a35d5f http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commit;h=36d51afa45c00710c6cfa07c00928ca235999c2d http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commit;h=b752821e1ca5c14817bbb8955d2f0f3ac2f327e9 http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commit;h=d8faca64955bbe4ad23d90b16ec1fa41ad322c03 http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commit;h=8d3c66ca6a40dff64708fb26218e36fde2bd6cf7 http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commit;h=96e97b2b6a80c10bad7a9da4ad88adf90644a974
The following HornetQ server sub-resources are exposed in the AS console: security setting, address setting, JMS topic, JMS queue, role, connection factory. Additionally, the default HornetQ (delivered with full-ha profile for standalone) has sub-resources preconfigured out-of-box of the following types: remote connector, remote acceptor, pooled connection factory, in vm acceptor, in vm connector, discovery group, broadcast group.
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.