Red Hat Bugzilla – Bug 1015504
DLQ and ExpiryQueue queues have not set default Security Configurations
Last modified: 2014-01-02 15:33:25 EST
Description of problem: DLQ and ExpiryQueue queues have not set default Security Configurations. This gives error to user in JON UI. Version-Release number of selected component (if applicable): JON 3.2.0.ER2 + EAP 5.2.0.GA How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The Security Configurations shouldn't be enforced see https://bugzilla.redhat.com/show_bug.cgi?id=1019100
From user point of view. If I have working configuration set on the managed server, then trying to change any configuration attribute shouldn't be enforced by changing configuration of some different unrelated attribute in the configuration of the same resource. For example in this case for changing maximum length of Queue to be forced to set Security Configurations.
(same commit as for bug 1019100) branch: release#jon3.2.x link: http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?id=b69353ea3 time: 2013-10-17 19:02:32 +0200 commit: b69353ea32edb5fe790513fb51bf3efd32aafcbd author: Jirka Kremser - jkremser@redhat.com message: [BZ 1019100] - Definition of security constrain per Queue/Topic creation shouldn't be enforced - there is no need to require at least two items of "Security Configurations". The security for topics/queues can be set globally somewhere else or even turned off.
Moving to ON_QA for testing in the next build.
There is another value which is required to change in order to save configuration, I put it to separate BZ#1025812. The security constrain is no longer enforced and the other issue is tracked in separate BZ.