[jboss-jira] [JBoss JIRA] (WFLY-9854) jgroups-channel cannot use name which is already used by jgroups/stacks

[Paul Ferraro (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-9854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538148#comment-13538148 ] 

Paul Ferraro commented on WFLY-9854:
------------------------------------

[~eduda] Is there a practical basis for this jira?  If so, where did this configuration come from?  Why would anyone set jgroups-channel to "udp"?  That's not a realistic logical cluster name - and I would be surprised (even given WFLY-5459) that anyone would think this made sense.
If there is no practical basis for this jira, I would still reject it.  The idea that attribute constraints can never be made more restrictive is both unrealistic and counterproductive, as it means we could never have introduced capability constraints.

If anything, this is a bug in the previous release, as this value had no validation.  Even so, there are limits to the extent to which this attribute (or for the logical cluster name of any JGroups channel, in general) could ever be validated, as it can only be known at runtime that you are receiving messages from cluster members to which you did not intend.

> jgroups-channel cannot use name which is already used by jgroups/stacks
> -----------------------------------------------------------------------
>
>                 Key: WFLY-9854
>                 URL: https://issues.jboss.org/browse/WFLY-9854
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering, JMS
>    Affects Versions: 12.0.0.Beta1
>            Reporter: Erich Duda
>            Assignee: Paul Ferraro
>            Priority: Blocker
>
> The configuration \[1\] results to an error \[2\]. This is backward compatibility issue since the configuration works with previous releases of Wildfly.
> \[1\]
> {code:xml}
> <broadcast-group name="bg-group1" jgroups-stack="udp" jgroups-channel="udp" broadcast-period="2000" connectors="connector"/>
> {code}
> \[2\]
> {code}
> 10:52:29,982 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 15) WFLYCTL0013: Operation ("add") failed - address: ([
>     ("subsystem" => "jgroups"),
>     ("channel" => "udp")
> ]) - failure description: "WFLYCTL0436: Cannot register capability 'org.wildfly.clustering.jgroups.channel-factory.udp' at location '[
>     (\"subsystem\" => \"jgroups\"),
>     (\"channel\" => \"udp\")
> ]' as it is already registered in context 'global' at location(s) '[[
>     (\"subsystem\" => \"jgroups\"),
>     (\"stack\" => \"udp\")
> ]]'"
> {code}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)