Bug 952566

Summary: It is possible to create broadcast group using non-existent connectors
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Jakub Cechacek <jcechace>
Component: JMSAssignee: Jeff Mesnil <jmesnil>
Status: CLOSED CURRENTRELEASE QA Contact: Jakub Cechacek <jcechace>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: istudens, jkudrnac, mnovak
Target Milestone: ER1   
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 16:48:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jakub Cechacek 2013-04-16 08:31:44 UTC
It is possible to create broadcast group using non-existent connectors. It seems that validation is missing for add operation. This affects both CLI and Amin console, thus I suppose that problem is in underlying Management API. 

Example:

1. Creation of new group with non-existent connectors "ab" and "ba" will succeed 

[standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=default/broadcast-group=foo:add(socket-binding=default, connectors=[ab,ba]) 
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}

2. However if we try to change the value of connectors attribute to the very same value it will fail
 
/subsystem=messaging/hornetq-server=default/broadcast-group=foo:write-attribute(name=connectors,value=[ab,bc])
{
    "outcome" => "failed",
    "failure-description" => "JBAS011680: The broadcast group 'foo' defines reference to nonexistent connector 'ab'. Available connectors '[netty, in-vm, netty-throughput]'.",
    "rolled-back" => true,
    "response-headers" => {"process-state" => "reload-required"}
}

Comment 1 JBoss JIRA Server 2013-04-17 10:08:19 UTC
Jeff Mesnil <jmesnil> made a comment on jira AS7-6927

PR for master branch

Comment 2 Ivo Studensky 2013-08-29 13:59:47 UTC
Is there any plan to fix this in EAP?

Comment 4 Miroslav Novak 2013-09-23 10:08:48 UTC
Verified in EAP 6.2.0.ER1. Thanks for the fix!