Bug 1015504 - DLQ and ExpiryQueue queues have not set default Security Configurations
Summary: DLQ and ExpiryQueue queues have not set default Security Configurations
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 5
Version: JON 3.2
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ER04
: JON 3.2.0
Assignee: Jirka Kremser
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On: 1019100
Blocks: 1012435
TreeView+ depends on / blocked
 
Reported: 2013-10-04 12:09 UTC by Libor Fuka
Modified: 2014-01-02 20:33 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-02 20:33:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1025812 0 unspecified CLOSED Changing of Queue configuration requires to set expiry queue 2021-02-22 00:41:40 UTC

Internal Links: 1025812

Description Libor Fuka 2013-10-04 12:09:23 UTC
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:

Comment 1 Radim Hatlapatka 2013-10-15 08:00:39 UTC
The Security Configurations shouldn't be enforced see https://bugzilla.redhat.com/show_bug.cgi?id=1019100

Comment 2 Radim Hatlapatka 2013-10-15 08:43:40 UTC
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.

Comment 3 Jirka Kremser 2013-10-17 17:08:57 UTC
(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
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.

Comment 4 Simeon Pinder 2013-10-24 04:09:26 UTC
Moving to ON_QA for testing in the next build.

Comment 5 Radim Hatlapatka 2013-11-01 16:18:20 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.