[
https://issues.jboss.org/browse/WFLY-9854?page=com.atlassian.jira.plugin....
]
Jason Greene commented on WFLY-9854:
------------------------------------
Just responding to the ask, that I agree its not a compatibility concern. Anything that
was previously invalid but did not generate an error may generate an error in the future.
In some cases we can try to be nice and be liberal in what we accept, but thats not always
practical.
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)